1 |
El mar, 14-10-2008 a las 18:24 -0700, Alec Warner escribió: |
2 |
> On Tue, Oct 14, 2008 at 3:34 PM, Petteri Räty <betelgeuse@g.o> wrote: |
3 |
> >> |
4 |
> > |
5 |
> > There's no need to commit straight to stable. Just make two different |
6 |
> > new revisions for each EAPI. Then the arch teams can test it like usual. |
7 |
> |
8 |
> Aha a perfect canidate use case for GLEP 55[1] that fends off 'why are |
9 |
> there multiple versions of the same package' questions and |
10 |
> complexities. |
11 |
> |
12 |
|
13 |
If you're thinking about having two equal versions with different EAPIs, |
14 |
that's not allowed by GLEP 55: |
15 |
|
16 |
"Note that it is still not permitted to have more than one ebuild with |
17 |
equal category, package name, and version. Although it would have the |
18 |
advantage of allowing authors to provide backwards compatible ebuilds, |
19 |
it would introduce problems too. The first is the requirement to have |
20 |
strict EAPI ordering, the second is ensuring that all the ebuilds for a |
21 |
single category/package-version are equivalent, i.e. installing any of |
22 |
them has exactly the same effect on a given system." |
23 |
|
24 |
Regards, |
25 |
-- |
26 |
Santiago Moisés Mola |
27 |
Jabber: cooldwind@×××××.com | GPG: AAD203B5 |