1 |
El sáb, 16-06-2012 a las 15:31 +0100, Ciaran McCreesh escribió: |
2 |
> On Sat, 16 Jun 2012 16:29:09 +0200 |
3 |
> Pacho Ramos <pacho@g.o> wrote: |
4 |
> > I thought last Zac suggestion of ABI_SLOT modified to use |
5 |
> > "SLOT=ble/bla" was clear enough and we reached a consensus. |
6 |
> |
7 |
> Possibly. I'm waiting to see an implementation, a bunch of examples and |
8 |
> a comparison with just using SLOT and := or :*. |
9 |
> |
10 |
|
11 |
I cannot provide you an implementation as I don't have enough skills to |
12 |
do it, no idea if maybe other dev/people could help on this :/ |
13 |
|
14 |
Regarding the comparison with using only SLOT, the most clear example of |
15 |
how that solution was a bit worse was that glib vs |
16 |
dbus-glib/gobject-introspection handling: |
17 |
- Using only SLOT with := would end up with we needing to update ebuilds |
18 |
for packages depending on glib on each SLOT bump, that is completely |
19 |
inviable. |
20 |
- I suggested then to be able to make that packages depend on :* (for |
21 |
example, dev-libs/glib:2.*:=, that way, that packages wouldn't need to |
22 |
get their ebuilds updated as they would still fit inside "2.*" case, but |
23 |
would still get rebuild (as wanted) due := usage... but you also didn't |
24 |
like this approach. |
25 |
- Finally, we ended with SLOT="2/2.32" solution and packages depending |
26 |
on SLOT=2 (as currently) with the addition of ":=" to get them rebuild |
27 |
when "/2.32" changes. |
28 |
|
29 |
|
30 |
> > About what I am trying to solve, I have explained it multiple times in |
31 |
> > involved thread and won't repeat them once again. |
32 |
> |
33 |
> Describing the problem clearly and correctly, and in the appropriate |
34 |
> amount of generality, is the hardest and most important part of the |
35 |
> process. Figuring out what we're trying to solve is far harder than |
36 |
> writing a bit of code. |
37 |
> |
38 |
|
39 |
What I try to do is to replace the needing of manually rebuilding |
40 |
packages after updates due ABI changes, like currently occurs with xorg |
41 |
drivers, g-i and dbus-glib, ocaml-c based apps and cases like that. |
42 |
|
43 |
Regarding other problems like needing to use perl-cleaner, |
44 |
python-updater looks to be covered by another approach of "dynamic |
45 |
slots" I have just seen in gentoo-dev IRC channel by mgorny, then, that |
46 |
kind of issues would be uncovered with this (but maybe I am wrong as I |
47 |
know Zac had a more clear conception about how this ABI_SLOT way would |
48 |
work and what would it cover) |