1 |
Rich Freeman <rich0@g.o> wrote: |
2 |
> On Sun, Apr 5, 2015 at 11:47 AM, Martin Vaeth <martin@×××××.de> wrote: |
3 |
>> One suggestion around this problem would be to use different |
4 |
>> directories for these two types of use-flags, say |
5 |
>> "package.use" and "package.use.needed". |
6 |
> |
7 |
> I still think we need a better long-term solution, but the workaround |
8 |
> is simpler than that. |
9 |
> |
10 |
> I try to keep files in directories for package.keywords and |
11 |
> package.use. One starts with a z and is a dumping ground for |
12 |
> auto-whatever. |
13 |
|
14 |
So you use package.use/z instead of package.use.needed |
15 |
as in my suggestion. (In fact, I do currently a similar |
16 |
thing, only that I use a file named zzz_autounmask, |
17 |
because this is even later in the alphabet). |
18 |
|
19 |
I think it would be more transparent to the user if |
20 |
really a dedicated directory/file would be used and not |
21 |
some which "by accident" is the last in the alphabet. |
22 |
|
23 |
Anyway, this is a minor issue. |
24 |
The main problem is how to cleanup this directory/file |
25 |
(no matter how it is called). |
26 |
|
27 |
Currently, the only way to do this, is to remove this |
28 |
file and to hope that portage can recreate it. |
29 |
Unfortunately, quite often portage is not able to do this. |
30 |
The problem is at least NP hard, so probably any |
31 |
backtracking value just is too low. |
32 |
|
33 |
If portage would use the old values as a hint, how |
34 |
conflicts might possibly be resolved, perhaps this |
35 |
algorithm might be improved. |
36 |
|
37 |
> However, I think a cleaner solution would be better... |
38 |
|
39 |
++ |
40 |
|
41 |
My suggestion is something in between - less invasive |
42 |
(and, in particular, less time consuming) |
43 |
than your suggestion to recalculate the USE-settings |
44 |
with every emerge, but more automatic than the current state. |
45 |
|
46 |
With my suggestion the USE-settings have to be recalculated |
47 |
only if a special command is used (or - as currently - |
48 |
if resolving is not possible without changing USE-flags). |
49 |
|
50 |
Probably other approaches are possible, too. |