| 1 |
On 04/01/2010 01:44 PM, Róbert Čerňanský wrote: |
| 2 |
> If I'm getting this right the proposed behavior is such that in case of |
| 3 |
> conflicting use flags emerge fails and user gets a message that he |
| 4 |
> has to set use flags as required. If so then I think it is not the right |
| 5 |
> way to handle it. A package manager should be able do deal with (use |
| 6 |
> flag) dependencies automatically. Similarly as it deals with "normal" |
| 7 |
> package dependenicies. |
| 8 |
> |
| 9 |
> It should not do this silenly though. emerge -pv should display real |
| 10 |
> state of use flags; so if some use flag has to be turned on |
| 11 |
> automatically due to dependency/conflict then it has to be shown so. |
| 12 |
> |
| 13 |
> This apply also for package[use_flag] deps. It is not very convenient |
| 14 |
> to fiddle use flags for individual packages that I basically do not care |
| 15 |
> about because they are just dependencies; so natural expectation is |
| 16 |
> that package manager pulls required deps. automatically (whether it |
| 17 |
> means install a package or install a package _with_ switched use flag). |
| 18 |
> |
| 19 |
> I hope this does not sound that I'm dictating you what is the right way |
| 20 |
> to do things. I just wanted to express my opinion. And I admit that |
| 21 |
> perhaps I do not see possible negative consequences of such behaviour. |
| 22 |
|
| 23 |
I appreciate your input, and I think you're right about this issue. |
| 24 |
However, it seems to be essentially a user interface issue, and |
| 25 |
therefore it doesn't necessarily need to be included in the |
| 26 |
specification (except maybe as a side note). |
| 27 |
-- |
| 28 |
Thanks, |
| 29 |
Zac |
Archives