1 |
On Thu, Aug 11, 2011 at 1:31 AM, Zac Medico <zmedico@g.o> wrote: |
2 |
> On 08/10/2011 02:14 PM, Fabio Erculiani wrote: |
3 |
>> The problem here is that Portage enforces the same rule by trying to |
4 |
>> schedule the PDEPEND "as soon as possible" |
5 |
> |
6 |
> This behavior was introduced in order to solve bug 180045 [1]. |
7 |
> |
8 |
> We can accomplish similar results to the ASAP ("as soon as possible") |
9 |
> behavior in cases like this, if we create a virtual/meta-package that |
10 |
> pulls in the circularly dependent packages. We also havo to update the |
11 |
> reverse dependencies to refer to the virtual/meta-package. |
12 |
|
13 |
In case of dev-java/jdom and dev-java/jdom-jaxen my idea was to create |
14 |
virtual/jdom (having it to pull in both deps in RDEPEND) and update |
15 |
the reverse dependencies. Waiting to hear back from Java herd (Caster, |
16 |
actually). |
17 |
|
18 |
OTOH, I think that the gray area should be cleared out by clearly |
19 |
stating what is legal or not in an updated EAPI. Isn't that |
20 |
reasonable? |
21 |
|
22 |
> |
23 |
> So, the ASAP behavior is really just a convenience so that ebuild |
24 |
> maintainers don't have to go to the trouble of creating a virtual and |
25 |
> updating all the reverse dependencies. |
26 |
> |
27 |
> [1] http://bugs.gentoo.org/show_bug.cgi?id=180045 |
28 |
> -- |
29 |
> Thanks, |
30 |
> Zac |
31 |
> |
32 |
> |
33 |
|
34 |
|
35 |
|
36 |
-- |
37 |
Fabio Erculiani |