From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <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: Sat, 6 Apr 2013 11:13:36 -0400 [thread overview]
Message-ID: <CAJ0EP409h7TzJg+kbnOip2ggHL+=ZSX_5bsa__wjBT4fF5B3gQ@mail.gmail.com> (raw)
In-Reply-To: <20130406170909.38501493@portable>
On Sat, Apr 6, 2013 at 11:09 AM, Alexis Ballier <aballier@gentoo.org> wrote:
> On Sat, 6 Apr 2013 11:02:14 -0400
> Mike Gilbert <floppym@gentoo.org> wrote:
>
>> On Sat, Apr 6, 2013 at 10:33 AM, Alexis Ballier <aballier@gentoo.org>
>> 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 ?
>> >
>>
>> Well, ideally you would do it in conjunction with a version bump
>> rather than a revbump.
>>
>> But failing that, a revbump for an EAPI + dependency change seems like
>> the safest option.
>>
>
> or: we can do the conversion in place, tell people to
> @preserve-rebuild / revdep-rebuild and get the benefits next time :)
>
I'm just not sure how the package managers like an in-place EAPI
change. If it works, great.
next prev parent reply other threads:[~2013-04-06 15:14 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 [this message]
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
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='CAJ0EP409h7TzJg+kbnOip2ggHL+=ZSX_5bsa__wjBT4fF5B3gQ@mail.gmail.com' \
--to=floppym@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