On Aug 31, 2011, at 15:25, Ryan Schmidt wrote: > On Aug 31, 2011, at 10:37, Bradley Giesbrecht wrote: > >> My understanding for the use of sbin was mistaken. My reason for putting >> this script in sbin was to avoid a conflict with port svg2pdf; evidently a >> bad idea. >> >> I believe the port sources for svg2pdf are unmaintained and obsolete. In my >> experience, and others I have conferred with, the pdf files produced by the >> svg2pdf program are of poor quality. >> >> A solution to librsvg incorrectly installing sbin/svg2pdf could be to >> replace/conflict the ports librsvg and svg2pdf. >> >> Another solution would be to rename the librsvg svg2pdf script to something >> like rsvg2pdf. > > Since the svg2pdf software is unmaintained and its output is bad, it sounds > to me like making svg2pdf replaced_by librsvg would be ok. You might have to > do some pre-activate magic to deactivate an already-installed svg2pdf port.
Alternately, what if you kept the svg2pdf port, made it depend on librsvg, and just made it install this one shell script? _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
