1 |
On Tue, 18 Sep 2012 22:51:04 +0200 |
2 |
Michał Górny <mgorny@g.o> wrote: |
3 |
> On Tue, 18 Sep 2012 20:44:33 +0100 |
4 |
> Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
5 |
> > On Tue, 18 Sep 2012 12:40:51 -0700 |
6 |
> > Zac Medico <zmedico@g.o> wrote: |
7 |
> > > On 09/18/2012 12:29 PM, Ciaran McCreesh wrote: |
8 |
> > > > On Tue, 18 Sep 2012 12:25:57 -0700 |
9 |
> > > > Zac Medico <zmedico@g.o> wrote: |
10 |
> > > >> Also, if we change the meaning of RDEPEND in the next EAPI, so |
11 |
> > > >> that it's a hard build-time dep like DEPEND, then |
12 |
> > > >> DEPEND="${RDEPEND} virtual/pkgconfig" can be reduced to |
13 |
> > > >> DEPEND="virtual/pkgconfig". This is what I would like to do for |
14 |
> > > >> the experimental EAPI 5-hdepend which is planned [1]. |
15 |
> > > > |
16 |
> > > > What're we going to do about the zillions of unsolvable cycles |
17 |
> > > > that that would create? (Does Portage detect those and error out |
18 |
> > > > yet?) |
19 |
> > > |
20 |
> > > Yeah, it would be treated just like a DEPEND cycle, which is |
21 |
> > > already detected and treated as a fatal error. As a result, when |
22 |
> > > bumping the EAPI of an ebuild, you may have to migrate some deps |
23 |
> > > from RDEPEND to PDEPEND in order to solve the cycles. |
24 |
> > |
25 |
> > What about the large number of RDEPENDs that are required for a |
26 |
> > package to be usable, but not for it to be installed? |
27 |
> |
28 |
> They will still be RDEPEND, just installed earlier I believe. Except |
29 |
> for those arising conflicts which will have to be moved to PDEP. But |
30 |
> I think Zac said that already. |
31 |
|
32 |
...but you can't move them to be a PDEPEND, since PDEPENDs aren't |
33 |
guaranteed to be installed when a package is used. |
34 |
|
35 |
-- |
36 |
Ciaran McCreesh |