On Aug 12, 2007, at 15:08, Weissmann Markus wrote:
Just before this one gets a stopper for a lot of ports:Juan will look into doing a 1.5.2 (or whatever) release which includes the fix for the "/Applications" bug and also turns the violation errors into non-fatal warnings (for now). I should have done it this way from the start, to let us do some cleaning before the fist of quality assurance hits our ports.
I think having a whitelist is always going to be troublesome. Take cross-compilers: The standard layout for a cross-compiler toolchain on all systems is:
${prefix}/<host tuple>
eg:
${prefix}/arm-apple-darwin
It seems like it would make much more sense to use a blacklist that
catches common errors, rather than a whitelist that catches anything
that can't be easily pre-defined.
-landonf
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
