xmlpatch @0.3.3 Initial submission

[twic@…]

I have put together a port for the xmlpatch library:

​http://xmlpatch.sourceforge.net/
​http://sourceforge.net/projects/xmlpatch/

[twic@…]

Portfile

[twic@…]

patch-tests-check_diff.c.diff

[twic@…]

One question. I have called this port 'xmlpatch'. That's the name of the project on SourceForge, and it seems like a reasonable name. However, the upstream author has done some packaging for Debian, where he calls it 'libxmlpatch'; because this project contains an executable as well as a library, that seems wrong, so i did not follow suit. Did i do the right thing?

[ak.ml@…]

Cc Me!

[ryandesign@…]

The name "xmlpatch" seems fine. In MacPorts we usually go by what the upstream project calls it, and don't go prepending "lib" to things that are nevertheless libraries.

[ryandesign@…]

Committed in r86249 with these changes:

• Instead of setting distfiles and worksrcdir, just set distname
• Rewrote the glib2 dependency so glib2-devel could satisfy it
• Used rmd160 and sha256 checksums
• Rewrote master_sites to avoid redirects
• Some whitespace changes and moved lines
• Corrected license (the source files say "version 2.1 of the License, or (at your option) any later version")
• Also installed documentation files (see PortfileRecipes)