1 |
Dnia 2014-07-27, o godz. 17:08:27 |
2 |
Rich Freeman <rich0@g.o> napisał(a): |
3 |
|
4 |
> On Sun, Jul 27, 2014 at 4:24 PM, Michał Górny <mgorny@g.o> wrote: |
5 |
> > Dnia 2014-07-27, o godz. 10:42:19 |
6 |
> > |
7 |
> > Consider the following: |
8 |
> > |
9 |
> > 1. A depends on B, both are installed, |
10 |
> > |
11 |
> > 2. dependency on B is removed, emerge --depclean uninstalls B thanks |
12 |
> > to dynamic-deps, |
13 |
> > |
14 |
> > 3. B is treecleaned (nothing depends on it), |
15 |
> > |
16 |
> > 4. old version of A is removed (user doesn't update it yet), therefore |
17 |
> > dependency on B is restored from vdb. |
18 |
> > |
19 |
> > So, now user has package A installed which has unsatisfied dependency |
20 |
> > on non-available package. |
21 |
> |
22 |
> I'd think that portage should update vdb as soon as it detects the |
23 |
> dependency change. Then B would no longer depend on A in vdb. It |
24 |
> shouldn't hold onto outdated information. |
25 |
|
26 |
You just introduced the opposite breakage -- when a dependency on C was |
27 |
added, it ends up in vdb before C is installed. Now if C and current |
28 |
version of A are removed before C gets installed, you end up having |
29 |
broken dependency in vdb... |
30 |
|
31 |
Plus, 'as soon' means you're making --pretend actually write something. |
32 |
That's bad. |
33 |
|
34 |
-- |
35 |
Best regards, |
36 |
Michał Górny |