On Friday,  9 June 2006 at  8:53:47 -0400, John Baldwin wrote:
> On Wednesday 07 June 2006 20:48, Greg 'groggy' Lehey wrote:
>> On Wednesday,  7 June 2006 at 10:51:45 -0400, John Baldwin wrote:
>>> I thought the obfuscation was intentional as very few people should
>>> be doing a 'make world' without a custom DESTDIR these days.
>>
>> Then there's no reason not to document it.
>>
>>   Warning: FORCE_ROOT_INSTALL can render your system unusable by
>>   overwriting existing configuration files.  Do not use it unless you
>>   are completely aware of the consequences.
>>
>> And yes, a descriptive name like FORCE_ROOT_INSTALL, not
>> HISTORICAL_MAKE_WORLD.
>
> Describing it would subvert the intended obfuscation.

s/subvert/correct/

Obfuscation is always wrong.  

>> The only justification for this regression is that it's really
>> difficult to get everything right.  But that's a bug, not a
>> feature.
>
> No, the justification is that 'make world' completely ignores the
> kernel and only handles userland, and an operating system is both a
> kernel and a userland and that users should update those together.

That's a bug in make world.  Introducing a second one doesn't fix it.

> If you as a developer want to use make world you can either run the
> two commands back to back or you can put
> I_REALLY_KNOW_WHAT_IM_DOING_AND_WANT_TO_HOSE_MY_MACHINE in make.conf
> or something.  However, developers wanting to do this are in the
> _VAST_ minority and I'd much rather cater to the other 99% of the
> world.

As I say,

>> The only justification for this regression is that it's really
>> difficult to get everything right.

Otherwise people would have fixed it.

Greg
--
See complete headers for address and phone numbers.

Attachment: pgpoFdsQCeIBf.pgp
Description: PGP signature

Reply via email to