El mar, 17-01-2012 a las 18:23 +0100, "Paweł Hajdan, Jr." escribió: > On 1/16/12 12:36 PM, Pacho Ramos wrote: > > I agree but, why not *also* make portage warn people when they are > > exporting some "known to break" variables in their make.conf? > > That'd require coming up with such list of "known bad" variable names, > and generally I don't think blacklisting is very effective. > > It's relatively easy to invent a breaking name, but hard to enumerate > them all. > > Anyway, that's a superset of my original proposal, so I'm fine if > someone wants to experiment with it. >
The idea would be to fill that list when we get a bug report with user having problems due a variable and, then, prevent it from occurring in the future. This is similar to add "unset BLABLABLA" to our ebuilds when we get a bug report but with the advantage of covering more possible packages that could fail if the same variable is set.
signature.asc
Description: This is a digitally signed message part
