From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)
Date: Sun, 07 Apr 2013 20:06:44 -0400 [thread overview]
Message-ID: <51620A14.4020705@gentoo.org> (raw)
In-Reply-To: <20130406163357.53fc91be@portable>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 06/04/13 10:33 AM, Alexis Ballier wrote:
> On Fri, 05 Apr 2013 22:18:22 -0400 Ian Stakenvicius
> <axs@gentoo.org> wrote:
>
>>
>> Revbump -- very important in this case, as the slot-operator dep
>> (iirc) does not take effect to allow sub-slot-triggered until
>> after a version with the slot-operator has been emerged.
>>
>> So we want users to re-emerge packages either at the same time
>> libpng-1.6 hits the tree, or beforehand so that they will be
>> triggered for rebuild when libpng-1.6 hits.
>>
>
>
> so we force two rebuilds instead of one ?
>
Either we time it so they just rebuild at the same time (ie when the
package is unmasked or stable-keyworded), or we commit the revbump
earlier which would force a superfluous rebuild.
Technically there could (in theory at least) be a way of rewriting the
vdb to have the correct sub-slot entries (i had a script that did this
during my EAPI=4-slot-abi testing) but this isn't particularily safe
and would probably cause more issues for end users than the libpng-1.6
bump WITHOUT slot-operatored rdeps.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iF4EAREIAAYFAlFiChMACgkQ2ugaI38ACPBtYAD/YWxxprE1szh2meJVBt16Q+8x
it+AvHEbMiRetCHchoUA/R0Nkw0Tg6zrx0jO/RgA5U4/H6GGWZUO27VYz8TFu5ae
=yIRc
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-04-08 0:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 20:44 [gentoo-dev] libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting) Samuli Suominen
2013-04-05 21:17 ` Pacho Ramos
2013-04-05 21:22 ` Ian Stakenvicius
2013-04-05 21:43 ` Samuli Suominen
2013-04-05 21:44 ` Samuli Suominen
2013-04-05 21:27 ` Michael Mol
2013-04-05 21:46 ` Mike Gilbert
2013-04-06 1:52 ` Ben de Groot
2013-04-06 2:18 ` Ian Stakenvicius
2013-04-06 14:33 ` Alexis Ballier
2013-04-06 15:02 ` Mike Gilbert
2013-04-06 15:09 ` Alexis Ballier
2013-04-06 15:13 ` Mike Gilbert
2013-04-06 15:27 ` Ciaran McCreesh
2013-04-06 15:36 ` Alexis Ballier
2013-04-08 0:34 ` Ian Stakenvicius
2013-04-08 0:06 ` Ian Stakenvicius [this message]
2013-04-06 3:24 ` Alexandre Rostovtsev
2013-04-09 7:27 ` Sergey Popov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51620A14.4020705@gentoo.org \
--to=axs@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox