Opened 12 years ago

Closed 12 years ago

#31733 closed submission (fixed)

xmlpatch @0.3.3 Initial submission

Reported by: twic@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: ak.ml@…
Port: xmlpatch

Attachments (2)

Portfile (1.5 KB) - added by twic@… 12 years ago.
Portfile
patch-tests-check_diff.c.diff (353 bytes) - added by twic@… 12 years ago.
patch-tests-check_diff.c.diff

Download all attachments as: .zip

Change History (6)

Changed 12 years ago by twic@…

Attachment: Portfile added

Portfile

Changed 12 years ago by twic@…

patch-tests-check_diff.c.diff

comment:1 Changed 12 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:2 Changed 12 years ago by ak.ml@…

Cc: ak.ml@… added

Cc Me!

comment:3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned

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.

comment:4 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: assignedclosed

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)
Note: See TracTickets for help on using tickets.