> I'd like to commit just the first half of the patch, which introduces the -q > flag to reinplace, and release that with 2.0.1 (without the flag (or absence > of it) actually doing anything). Then in a later release, we'll add the > actual warning message when the flag is not used. The reason is that in some > cases the author of a reinplace expects it to not do anything, and this would > cause superfluous warnings -- most annoyingly right now, thousands of them > (one per file in the distfile) for each kde4 portgroup port, and similarly > for documentation files in the mysql5 port. If we commit the flag now without > it doing anything, then later when we make the flag do something, we can > simultaneously update those few designed-to-not-do-anything reinplaces to use > the flag so they don't spew warnings.
Good approach since we're itching to get 2.0.1 out.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
