Opened 13 years ago
Last modified 13 years ago
#31733 closed submission
xmlpatch @0.3.3 Initial submission — at Version 3
| Reported by: | twic@… | Owned by: | ryandesign@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | Cc: | ak.ml@… | |
| Port: | xmlpatch |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
I have put together a port for the xmlpatch library:
http://xmlpatch.sourceforge.net/
http://sourceforge.net/projects/xmlpatch/
Change History (5)
Changed 13 years ago by twic@…
Changed 13 years ago by twic@…
| Attachment: | patch-tests-check_diff.c.diff added |
|---|
patch-tests-check_diff.c.diff
comment:1 Changed 13 years ago by 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?
comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|---|
| Owner: | changed from macports-tickets@… to ryandesign@… |
| Status: | new → assigned |
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.
Note: See
TracTickets for help on using
tickets.
Portfile