Gentoo Archives: gentoo-dev

From: Pacho Ramos <pacho@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] About what would be included in EAPI5
Date: Sat, 16 Jun 2012 14:49:52
Message-Id: 1339858100.7815.20.camel@belkin4
In Reply to: Re: [gentoo-dev] About what would be included in EAPI5 by Ciaran McCreesh
El sáb, 16-06-2012 a las 15:31 +0100, Ciaran McCreesh escribió:
> On Sat, 16 Jun 2012 16:29:09 +0200 > Pacho Ramos <pacho@g.o> wrote: > > I thought last Zac suggestion of ABI_SLOT modified to use > > "SLOT=ble/bla" was clear enough and we reached a consensus. > > Possibly. I'm waiting to see an implementation, a bunch of examples and > a comparison with just using SLOT and := or :*. >
I cannot provide you an implementation as I don't have enough skills to do it, no idea if maybe other dev/people could help on this :/ Regarding the comparison with using only SLOT, the most clear example of how that solution was a bit worse was that glib vs dbus-glib/gobject-introspection handling: - Using only SLOT with := would end up with we needing to update ebuilds for packages depending on glib on each SLOT bump, that is completely inviable. - I suggested then to be able to make that packages depend on :* (for example, dev-libs/glib:2.*:=, that way, that packages wouldn't need to get their ebuilds updated as they would still fit inside "2.*" case, but would still get rebuild (as wanted) due := usage... but you also didn't like this approach. - Finally, we ended with SLOT="2/2.32" solution and packages depending on SLOT=2 (as currently) with the addition of ":=" to get them rebuild when "/2.32" changes.
> > About what I am trying to solve, I have explained it multiple times in > > involved thread and won't repeat them once again. > > Describing the problem clearly and correctly, and in the appropriate > amount of generality, is the hardest and most important part of the > process. Figuring out what we're trying to solve is far harder than > writing a bit of code. >
What I try to do is to replace the needing of manually rebuilding packages after updates due ABI changes, like currently occurs with xorg drivers, g-i and dbus-glib, ocaml-c based apps and cases like that. Regarding other problems like needing to use perl-cleaner, python-updater looks to be covered by another approach of "dynamic slots" I have just seen in gentoo-dev IRC channel by mgorny, then, that kind of issues would be uncovered with this (but maybe I am wrong as I know Zac had a more clear conception about how this ABI_SLOT way would work and what would it cover)


File name MIME type
signature.asc application/pgp-signature


Subject Author
Re: [gentoo-dev] About what would be included in EAPI5 Ciaran McCreesh <ciaran.mccreesh@××××××××××.com>
Re: [gentoo-dev] About what would be included in EAPI5 "Michał Górny" <mgorny@g.o>
Re: [gentoo-dev] About what would be included in EAPI5 Peter Stuge <peter@×××××.se>