| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 24/01/13 01:55 PM, Michael Orlitzky wrote: |
| 5 |
> On 01/24/13 13:25, Rich Freeman wrote: |
| 6 |
>> On Thu, Jan 24, 2013 at 1:18 PM, Ian Stakenvicius |
| 7 |
>> <axs@g.o> wrote: |
| 8 |
>>> a fatal die in pkg_pretend could be circumvented by an |
| 9 |
>>> environment variable such as ${PN}_I_KNOW_WHAT_IM_DOING being |
| 10 |
>>> set. Just a thought. |
| 11 |
>> |
| 12 |
>> If we're going to do this I'd definitely have the ${PN} bit as |
| 13 |
>> you suggested. Otherwise everybody will just set it in make.conf |
| 14 |
>> and the feature will be pointless. Then we'll yell at users |
| 15 |
>> because they disabled the feature that normally just tends to |
| 16 |
>> break half their builds but this time by some miracle would have |
| 17 |
>> actually prevented a problem. |
| 18 |
> |
| 19 |
> Are there really that many ways that this could cause false |
| 20 |
> positives? (Not that I'm against the $PN prefix, just curious). |
| 21 |
> |
| 22 |
> I've only seen two legitimate examples: catalyst (whose developers |
| 23 |
> are more than capable of setting a variable) and a |
| 24 |
> supervisor-provided kernel for which you have no information. |
| 25 |
> |
| 26 |
|
| 27 |
How about, you know what you're doing and are going to build a new |
| 28 |
kernel as soon as the emerge finishes (since the emerge is also |
| 29 |
bringing in a new gentoo-sources)?? |
| 30 |
|
| 31 |
|
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 34 |
|
| 35 |
iF4EAREIAAYFAlEBhEsACgkQ2ugaI38ACPDYHAD/RCYlN6hcItJYn/gCcEdEgh+C |
| 36 |
owE/NaeGNDiH+3H/+uAA/jRfeJ+HPxDLdGNxt/VARcrqYnA15o6SmAiHOIj4i8Au |
| 37 |
=FTEj |
| 38 |
-----END PGP SIGNATURE----- |
Archives