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