the portfiles should be somewhat clean, now.
what remains (and that's more work) is patches. they're more complicated
because switching to ${prefix} requires either the use of 'reinplace' or
or a combination of the two. i've pasted a list[1]. it's the result of
grepping through */*/files/* so file likes e.g.[2] are included, too.
[1] http://rafb.net/p/HXnlzH86.html
[2] mail/imap-uw/files/README-MACOSX
Regards,
Elias
On Mar 26, 2007, at 9:18 PM, Kevin Van Vechten wrote:
On Mar 26, 2007, at 11:59 AM, Jordan K. Hubbard wrote:
That would be one way to do it. Another way would be to simply
sweep through the ports and correct them all at once. That would
certainly be a lot faster than waiting for n maintainers to wake
up, though I suppose it also wouldn't "teach them anything" either.
An observant maintainer would notice the change and learn from it
(isn't revision control great?).
I think sweeps across all ports to implement global policy best
serves the interest of the users of MacPorts. I think it's best to
view maintainers as the primary contributors to a port, and not
owners with veto power. I'm speaking as the maintainer of a few
ports myself, who doesn't have enough time to keep abreast of all
the latest and greatest MacPorts directions.
- kvv
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
