1 |
On Sat, 16 Jun 2012 16:48:20 +0200 |
2 |
Pacho Ramos <pacho@g.o> wrote: |
3 |
> Regarding the comparison with using only SLOT, the most clear example |
4 |
> of how that solution was a bit worse was that glib vs |
5 |
> dbus-glib/gobject-introspection handling: |
6 |
> - Using only SLOT with := would end up with we needing to update |
7 |
> ebuilds for packages depending on glib on each SLOT bump, that is |
8 |
> completely inviable. |
9 |
|
10 |
What about if ranged dependencies existed? |
11 |
|
12 |
Also, we've yet to establish whether SLOT-with-/ really solves this |
13 |
problem, nor whether the problem is a general one. How many packages |
14 |
are there with stable APIs but unstable ABIs? |
15 |
|
16 |
> - I suggested then to be able to make that packages depend on :* (for |
17 |
> example, dev-libs/glib:2.*:=, that way, that packages wouldn't need to |
18 |
> get their ebuilds updated as they would still fit inside "2.*" case, |
19 |
> but would still get rebuild (as wanted) due := usage... but you also |
20 |
> didn't like this approach. |
21 |
|
22 |
You're misunderstanding the point of the * there. The * has nothing to |
23 |
do with wildcarding. |
24 |
|
25 |
> > > About what I am trying to solve, I have explained it multiple |
26 |
> > > times in involved thread and won't repeat them once again. |
27 |
> > |
28 |
> > Describing the problem clearly and correctly, and in the appropriate |
29 |
> > amount of generality, is the hardest and most important part of the |
30 |
> > process. Figuring out what we're trying to solve is far harder than |
31 |
> > writing a bit of code. |
32 |
> |
33 |
> What I try to do is to replace the needing of manually rebuilding |
34 |
> packages after updates due ABI changes, like currently occurs with |
35 |
> xorg drivers, g-i and dbus-glib, ocaml-c based apps and cases like |
36 |
> that. |
37 |
|
38 |
See, that's not really a description of the problem. It's a good start, |
39 |
but I'd expect a full description to run to be several pages of |
40 |
detailed description of the general case, along with worked out |
41 |
examples. This isn't an easy issue, and we don't want to come up with a |
42 |
solution that works for one particular package whilst ignoring the |
43 |
needs of everything else. |
44 |
|
45 |
> Regarding other problems like needing to use perl-cleaner, |
46 |
> python-updater looks to be covered by another approach of "dynamic |
47 |
> slots" I have just seen in gentoo-dev IRC channel by mgorny, then, |
48 |
> that kind of issues would be uncovered with this (but maybe I am |
49 |
> wrong as I know Zac had a more clear conception about how this |
50 |
> ABI_SLOT way would work and what would it cover) |
51 |
|
52 |
Somehow I don't think this cunning plan has been thought all the way |
53 |
through... |
54 |
|
55 |
Coming up with a "solution" rather than a description of the problem is |
56 |
the wrong thing to do. |
57 |
|
58 |
-- |
59 |
Ciaran McCreesh |