1 |
On Tue, 18 Sep 2012 23:06:19 +0100 |
2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
3 |
|
4 |
> On Wed, 19 Sep 2012 00:01:21 +0200 |
5 |
> Michał Górny <mgorny@g.o> wrote: |
6 |
> > On Tue, 18 Sep 2012 22:37:19 +0100 |
7 |
> > Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
8 |
> > > On Tue, 18 Sep 2012 23:34:29 +0200 |
9 |
> > > Michał Górny <mgorny@g.o> wrote: |
10 |
> > > > On Tue, 18 Sep 2012 22:08:43 +0100 |
11 |
> > > > Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
12 |
> > > > > On Tue, 18 Sep 2012 23:06:06 +0200 |
13 |
> > > > > Michał Górny <mgorny@g.o> wrote: |
14 |
> > > > > > But didn't we already point out that we can't have them in |
15 |
> > > > > > RDEPEND since they introduce conflicts? |
16 |
> > > > > |
17 |
> > > > > You are missing a basic and important part of how dependency |
18 |
> > > > > resolution works: currently, cycles consisting purely of |
19 |
> > > > > RDEPENDs are ignorable. |
20 |
> > > > |
21 |
> > > > So, what do we lose? If PDEP comes 'ASAP' officially, I believe |
22 |
> > > > that we actually gain RDEPs which can be actually trusted. |
23 |
> > > |
24 |
> > > "ASAP" is a weaker guarantee that RDEPENDs currently have -- |
25 |
> > > RDEPENDs currently have the weakest guarantee necessary to ensure |
26 |
> > > that they can be trusted. It's also a useless guarantee, since |
27 |
> > > "ASAP" can be arbitrarily late. |
28 |
> > |
29 |
> > And can't RDEPENDs be arbitrarily late if there is a cycle? |
30 |
> |
31 |
> No. RDEPENDs have to be available when a package is used to satisfy a |
32 |
> dependency. That's the difference between an RDEPEND and a PDEPEND. |
33 |
|
34 |
So, if a particular cycle prohibits RDEPENDs being fulfilled when |
35 |
RDEPEND is needed to satisfy a dependency, we have a failure now, |
36 |
correct? |
37 |
|
38 |
Do we have that guarantee somewhere in the PMS? |
39 |
|
40 |
-- |
41 |
Best regards, |
42 |
Michał Górny |