| 1 |
On 06/11/2012 07:30 PM, Chris Stankevitz wrote: |
| 2 |
> On Mon, Jun 11, 2012 at 1:26 AM, Alex Schuster <wonko@×××××××××.org> wrote: |
| 3 |
>> I think Chris' question is more about why he has to manually activate |
| 4 |
>> this USE flag, as it seems to be necessary anyway, in his case. |
| 5 |
> |
| 6 |
> Alex, |
| 7 |
> |
| 8 |
> Yes this is correct. I see now I was far too wordy in the OP and |
| 9 |
> thank you for your terse translation! |
| 10 |
> |
| 11 |
> Typically when I solve a "gentoo system problem" by adding modifying |
| 12 |
> package.use, I am doing something wrong. (e.g. ruby_targets_ruby19). |
| 13 |
> |
| 14 |
> I gather that the udev/hwdb/udisk case is an exception. The "correct |
| 15 |
> way" to solve this "gentoo system problem" is to "echo sys-fs/udev |
| 16 |
> hwdb >> /etc/portage/package.use" |
| 17 |
|
| 18 |
Portage doesn't know what you want to do, so it does the safe thing and |
| 19 |
lets you decide. Either, |
| 20 |
|
| 21 |
a) You want USE="-hwdb", in which case emerging udisks is a mistake. |
| 22 |
|
| 23 |
b) You want to emerge udisks, in which case USE="-hwdb" is a mistake. |
| 24 |
|
| 25 |
The autounmask feature allows you to make (b) the default if that's what |
| 26 |
you want. |
| 27 |
|
| 28 |
The ruby_targets_ruby19 thing is a good example of where you may not |
| 29 |
want that behavior by default. Something was screwed up, people noticed |
| 30 |
it, and the devs ultimately fixed it. The most-correct thing to do was |
| 31 |
nothing (i.e. wait). |
Archives