1 |
On 08/10/2011 10:19 PM, Fabio Erculiani wrote: |
2 |
> On Thu, Aug 11, 2011 at 1:31 AM, Zac Medico <zmedico@g.o> wrote: |
3 |
>> On 08/10/2011 02:14 PM, Fabio Erculiani wrote: |
4 |
>>> The problem here is that Portage enforces the same rule by trying to |
5 |
>>> schedule the PDEPEND "as soon as possible" |
6 |
>> |
7 |
>> This behavior was introduced in order to solve bug 180045 [1]. |
8 |
>> |
9 |
>> We can accomplish similar results to the ASAP ("as soon as possible") |
10 |
>> behavior in cases like this, if we create a virtual/meta-package that |
11 |
>> pulls in the circularly dependent packages. We also havo to update the |
12 |
>> reverse dependencies to refer to the virtual/meta-package. |
13 |
> |
14 |
> In case of dev-java/jdom and dev-java/jdom-jaxen my idea was to create |
15 |
> virtual/jdom (having it to pull in both deps in RDEPEND) and update |
16 |
> the reverse dependencies. Waiting to hear back from Java herd (Caster, |
17 |
> actually). |
18 |
|
19 |
The ASAP behavior seems relatively optimal, which makes it difficult to |
20 |
argue that ebuild maintainers should have to go to the trouble of |
21 |
creating virtuals and updating reverse dependencies. |
22 |
|
23 |
It seems like your setting up an ongoing conflict with ebuild |
24 |
maintainers if you don't implement the ASAP behavior. Isn't it worth |
25 |
your trouble to implement the ASAP behavior, just to get them out of |
26 |
your hair? |
27 |
|
28 |
> OTOH, I think that the gray area should be cleared out by clearly |
29 |
> stating what is legal or not in an updated EAPI. Isn't that |
30 |
> reasonable? |
31 |
|
32 |
It's already been allowed for years, so a new EAPI would only make sense |
33 |
if your taking away the ASAP behavior, which seems like a step |
34 |
backwards. Given the push-back that you're likely to get from ebuild |
35 |
developers over time, I think you're much better off if you just |
36 |
implement the ASAP behavior. |
37 |
-- |
38 |
Thanks, |
39 |
Zac |