On 2007-08-29 23:29:11 -0500, Ryan Schmidt wrote: > Please don't make the notices fatal for everyone now. Port maintainers need > time to discover that their ports violate the mtree and figure out how to > fix it. mtree violations were fatal in 1.5.1 resulting in a torrent of > users complaining about ports they couldn't install and we had to do a > quick 1.5.2 to reduce them to warnings so that people could continue using > the software they wanted to use. I don't think anybody realized these mtree > errors would be occurring (except the author of the feature) until the > messages started pouring in. These messages are important to developers, > but users should not be inconvenienced by them. > > Given that more than half our ports are currently unmaintained (2111 out of > 4202), I'm unconvinced that mtree violations should ever be made fatal. > Doing so could inconvenience the users of many of our ports, and give them > the impression that MacPorts is broken or not ready for prime-time, > impressions I think we should strive to reduce, not increase.
Yes, but you didn't answer to the main point (that was already in my first message): in the meantime, what about making this configurable? -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
