| 1 |
On Wed, Feb 15, 2012 at 2:18 PM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Wed, 15 Feb 2012 13:00:57 -0800, Mark Knecht wrote: |
| 3 |
> |
| 4 |
>> > That behavior can be controlled by your FEATURES settings |
| 5 |
>> > (collision-protect or protect-owned) and optionally modified further |
| 6 |
>> > in make.conf by COLLISION_IGNORE. |
| 7 |
> |
| 8 |
>> Good to know. I guess the default setting must be to overwrite as I've |
| 9 |
>> not made any of those setting changes. |
| 10 |
> |
| 11 |
> emerge --info will show you the settings in use. |
| 12 |
> |
| 13 |
> |
| 14 |
> -- |
| 15 |
> Neil Bothwick |
| 16 |
|
| 17 |
Of course, but if you don't know about collision-protect, for |
| 18 |
instance, then how would one even know to put it there? |
| 19 |
|
| 20 |
man make.conf does show the collision-protect option, along with some |
| 21 |
others that look cool. I haven't read that man page in literally |
| 22 |
years, if not close to a decade! |
| 23 |
|
| 24 |
Cheers, |
| 25 |
Mark |
| 26 |
|
| 27 |
FEATURES="assume-digests binpkg-logs distlocks ebuild-locks fixlafiles |
| 28 |
news parallel-fetch preserve-libs protect-owned sandbox sfperms strict |
| 29 |
unknown-features-warn unmerge-logs unmerge-orphans userfetch" |
Archives