-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 05/08/13 12:10 PM, Michał Górny wrote: > Dnia 2013-08-05, o godz. 11:50:38 Alexis Ballier > <aball...@gentoo.org> napisał(a): > >> On Mon, 05 Aug 2013 18:06:33 +0300 Samuli Suominen >> <ssuomi...@gentoo.org> wrote: >>> The plan is to change SLOT of virtual/jpeg from "0" to eg. >>> "0/1" after next SONAME change in the default of the virtual, >>> so it's useful to have everything depend on virtual/jpeg:0= >>> ready, to get the benefits of the subslot. >> >> last I heard subslots on virtuals didnt work that well: >> https://bugs.gentoo.org/show_bug.cgi?id=449094 >> >> and this plan is broken: changing the subslot on the virtual >> will trigger the rebuilds but will likely not ensure all the >> providers have changed soname, so there is a case of completely >> useless rebuilds. >> >> I would rather wait for the above bug to be fixed and have a >> proper way to handle subslots through virtuals than converting >> packages to := depend on the virtual. > > We can simply have multiple virtual versions, each depending on the > proper jpeg & jpeg-turbo versions. >
...except it doesn't end up being that simple. Making sure the virtual and the dependents link up properly requires PDEPENDS on the dependents as well as proper DEPENDS on the virtuals, and <= deps (which don't play nice with anything). But yes, this is the best option at this point. [tangent] If it were still supported, what *would* work best would be the old PROVIDES= syntax within the dependent ebuilds. The main issue with sub-slot propagation is the fact that it needs to propagate through these 'virtual' packages. Except they aren't packages, they're just an alias for a set of (R)DEPEND values. The more i've thought about this, the more I'm thinking virtuals should be treated differently than what we're currently doing... [/tangent] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iF4EAREIAAYFAlIBAx0ACgkQ2ugaI38ACPAelQD+Ot+Jb3MVGy1pT+JDdWJ62g9D m4JcxZbohFI9Zblt6LYA/2ZQ2E7QByGLWaHMomrK0B5cSK7GNH3sJh9PrfXHgn5S =fXu5 -----END PGP SIGNATURE-----
