1 |
El mié, 06-06-2012 a las 18:16 +0100, Ciaran McCreesh escribió: |
2 |
> On Wed, 06 Jun 2012 11:48:26 +0200 |
3 |
> Pacho Ramos <pacho@g.o> wrote: |
4 |
> > That looks nice, only two notes: |
5 |
> > - Looks like would be more sense on distinguish between "SLOT" and |
6 |
> > ABI_SLOT, for example: |
7 |
> > * dbus-glib would rdepend on glib:2 |
8 |
> > * if glib:2 abi changes, we would pull a ABI_SLOT="2.32" |
9 |
> > inside glib-2 ebuild |
10 |
> > * dbus-glib rdepending on glib:=2 would get rebuilt |
11 |
> > If we would use "SLOT" for all the cases, how would we handle it? I |
12 |
> > mean, glib slot would be bumped to "2.32" and dbus-glib ebuilds |
13 |
> > updated to rdepend on every new slot? Or would package managers |
14 |
> > distinct between "versions" inside the same SLOT variable? |
15 |
> |
16 |
> You'd have a slot per ABI, and be encouraged to allow multiple versions |
17 |
> of glib to be installed in parallel. If you really couldn't do that |
18 |
> (and you should think very carefully before saying you can't, since |
19 |
> this directly affects users in a huge way), you can make the slots |
20 |
> block each other. |
21 |
|
22 |
Probably other gnome team could reply this better than me, but I don't |
23 |
think slotting every glib-2 due ABI changes deserves the huge effort. |
24 |
Also, we want people to rebuild them against, for example, glib-2.32 |
25 |
ABI, not to keep glib-2.30 and 2.32 installed in parallel and some |
26 |
packages built against 2.30 and others against 2.32. |
27 |
|
28 |
Also, how could this be handled in dbus-glib side? I mean, would we need |
29 |
to update dbus-glib update from RDEPENDing on glib:2.30 to glib:2.32? :O |
30 |
|
31 |
> |
32 |
> > - What would occur with packages forced to use eapi0 due backwards |
33 |
> > compat? We could probably deprecate eapis older than 5 to allow all |
34 |
> > the tree be consistent with this rebuilds forcing, but no idea what |
35 |
> > to do with system packages still needing to use eapi0 and maybe |
36 |
> > changing their ABI too :/ |
37 |
> |
38 |
> The situation for older packages remains the same. |
39 |
> |
40 |
|
41 |
Maybe we have a third option that could allow us to not use ABI_SLOT if |
42 |
you prefer: |
43 |
- eapi5 could allow the usage of depending on multiple slots, for |
44 |
example, dbus-glib would RDEPEND on dev-libs/glib:2.*:= |
45 |
Then, we would have dev-libs/glib:2.30 and dev-libs/glib:2.32, both |
46 |
mutually exclusive but ebuilds RDEPENDing on them not needing to be |
47 |
updated on every abi bump due them really working for both ABIs. |
48 |
- Package managers would still rebuild all apps with that ":=" syntax |
49 |
- We would be able to skip ABI_SLOT needing |
50 |
- If a package is RDEPENDing on an old eapi0 package, that package could |
51 |
still use SLOT="2.32" or "2.30" and eapi5 ebuild rdepending on it still |
52 |
behaving in the same way. |