| 1 |
On Sat, Aug 8, 2015 at 3:49 PM, Heiko Baums <lists@××××××××××××.de> wrote: |
| 2 |
> Am 08.08.2015 um 21:30 schrieb Rich Freeman: |
| 3 |
>> This was the subject of extensive discussion and a council decision. |
| 4 |
>> |
| 5 |
>> The rationale for not configuring the installing of small files via a |
| 6 |
>> USE flag is that it would greatly increase the number of packages that |
| 7 |
>> would depend on that flag, and then when a user swtiches their |
| 8 |
>> configuration they're rebuilding half their system just for the sake |
| 9 |
>> of a few dozen single-inode files. |
| 10 |
>> |
| 11 |
>> If people want to set install masks they can. However, this will come |
| 12 |
>> at the cost of having to rebuild half your system later if you change |
| 13 |
>> your mind. |
| 14 |
> |
| 15 |
> And what's the difference if I have to rebuild half my system because of |
| 16 |
> a USE flag or because of an INSTALL_MASK? |
| 17 |
|
| 18 |
It is recommended that users not set an INSTALL_MASK, so you won't |
| 19 |
have to rebuild anything if you don't do that. If you care that much |
| 20 |
about inodes I'd probably get rid of /usr/portage before |
| 21 |
/usr/lib/systemd. :) |
| 22 |
|
| 23 |
On the other hand, setting USE=systemd when you don't intend to use |
| 24 |
systemd is going to be more invasive in general for the packages that |
| 25 |
use that flag. So, you probably wouldn't want to do that. |
| 26 |
|
| 27 |
I'm sure there were about 85 posts on the lists taking your side when |
| 28 |
this was debated before. I'd suggest looking up the threads (about |
| 29 |
two years ago I think) rather than recreating them. |
| 30 |
|
| 31 |
-- |
| 32 |
Rich |
Archives