Gentoo Archives: gentoo-dev

From: Pacho Ramos <pacho@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Always specify SLOT we know a package is compatible with (even if only one SLOT exists at the moment ebuild is added)
Date: Sat, 19 Sep 2015 10:52:05
Message-Id: 1442659910.13037.21.camel@gentoo.org
In Reply to: Re: [gentoo-dev] Always specify SLOT we know a package is compatible with (even if only one SLOT exists at the moment ebuild is added) by hasufell
1 El sáb, 19-09-2015 a las 12:40 +0200, hasufell escribió:
2 > On 09/19/2015 12:36 PM, hasufell wrote:
3 > >
4 > >
5 > > I personally think
6 > > it is enough to do that for multislot packages.
7 > >
8 >
9 > And afais repoman already emits a warning for those on EAPI=5.
10 >
11 Yes, I know... this is about always setting the SLOT we know it does
12 work, even when only one SLOT exists (as the summary says) to prevent
13 we need to constantly fix RDEPENDs of all reverse deps every time a new
14 slot is added. This currently was a bit more "invisible" to users...
15 but once dynamic-deps are disabled, people will need to rebuild ALL
16 that reverse deps to get the proper (old) slot set in VDB.
17
18 In summary, this is the first suggestion of:
19 https://bugs.gentoo.org/show_bug.cgi?id=493742#c0
20
21 That it will know much more visible as, for example, at the time
22 gstreamer:1.0 was added, we were able to simply fix reverse deps to
23 pull in the old slot they were still using, but now, in addition to
24 that, people will need to also rebuild all the reverse deps for the
25 same purpose. If, at the start, that packages would have the proper
26 slot set that was working when the package was added/bumped, the deps
27 would have being ok for the first time and, then, no update of the
28 RDEPEND and no rebuild would be triggered

Replies