From: Hilco Wijbenga <hilco.wijbenga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Portage option "--changed-use" not working?
Date: Sat, 21 Jan 2012 15:45:25 -0800 [thread overview]
Message-ID: <CAE1pOi0+aQHayQqtvGWg673doAXJnDaQSujX6hGpHdNJojWKvg@mail.gmail.com> (raw)
In-Reply-To: <20120121132645.61340cd3@khamul.example.con>
On 21 January 2012 03:26, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Fri, 20 Jan 2012 11:00:52 -0600
> »Q« <boxcars@gmx.net> wrote:
>
>> On Fri, 20 Jan 2012 12:06:22 +0000
>> Neil Bothwick <neil@digimed.co.uk> wrote:
>>
>> > I suspect this is
>> > specific to the KDE ebuilds (or eclass). changed-use should only
>> > skip an ebuild with changed flags if re-emerging would produce
>> > exactly the same code as before, this may not be the case. For
>> > example, in some ebuilds, it is the absence of a USE flag that
>> > triggers an extra configure option, so removing that use flag would
>> > give the same code as if the package had been emerged with it
>> > enabled.
>> >
>> > Something like this happened recently with the nls flag on glibc.
>>
>> Ah, that makes sense -- thanks. (And now I wish I'd read the entire
>> thread in dev before I posted a few minutes ago.)
>>
>> IMO, the man page's section on --changed-use should say what you've
>> just said rather than what it says now.
>
> I saw the logs from the kde team meeting where they discussed removing
> kdeenablefinal and decided when to do it. My own update on that ran
> overnight so I wasn't too fazed.
>
> But is this not a case where the kde eclass *explictly* set the USE
> flag off? (Disclaimer: haven't read the eclass). In that case portage
> would not know what to do when the flag goes away so the behaviour we
> saw would not really be a bug, it would be "playing safe"
I do not quite follow your logic here. Whether a USE flag is forcibly
disabled, not enabled, or disabled by default, does not make any
practical difference: it is not used. So when it is then removed later
on, no rebuild is necessary. It was not used before, now it does not
even exist any more.
> --changed-use is intended for cases like a flag you are not using at
> all goes away. Caveat: Even then it could still break in subtle ways
> with dodgy ebuilds. Caveat emptor.
Which is *exactly* what happened here (IIUC). The use of
kdeenablefinal has been discouraged from the start [or at least for a
very long time] so I (and presumably most people) never enabled it.
Now it has been removed. Ergo: nothing needs to be rebuilt.
I do not think it makes sense to worry about dodgy ebuilds. If you go
down that road, you would have to rebuild *everything* every time
there is a change ... just in case. Dodgy ebuilds should be fixed, not
catered to.
next prev parent reply other threads:[~2012-01-21 23:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 19:07 [gentoo-user] Portage option "--changed-use" not working? Hilco Wijbenga
2012-01-19 21:30 ` [gentoo-user] " »Q«
2012-01-19 21:44 ` Hilco Wijbenga
2012-01-19 22:28 ` [gentoo-user] " Dale
2012-01-19 23:01 ` Hilco Wijbenga
2012-01-20 0:05 ` Dale
2012-01-20 0:15 ` Hilco Wijbenga
2012-01-20 1:38 ` Dale
2012-01-20 3:12 ` Hilco Wijbenga
2012-01-20 3:25 ` Dale
2012-01-20 3:50 ` Hilco Wijbenga
2012-01-20 9:07 ` Dale
2012-01-20 9:27 ` Neil Bothwick
2012-01-20 10:08 ` Dale
2012-01-20 12:06 ` Neil Bothwick
2012-01-20 12:21 ` Dale
2012-01-20 17:00 ` [gentoo-user] " »Q«
2012-01-21 11:26 ` Alan McKinnon
2012-01-21 23:45 ` Hilco Wijbenga [this message]
2012-01-22 0:16 ` Alan McKinnon
2012-01-22 2:23 ` »Q«
2012-01-22 4:34 ` Walter Dnes
2012-01-22 6:07 ` »Q«
2012-01-22 7:48 ` Dale
2012-01-22 8:40 ` Alan McKinnon
2012-01-22 11:09 ` Neil Bothwick
2012-01-20 16:53 ` »Q«
2012-01-20 18:37 ` Dale
2012-01-20 18:39 ` »Q«
2012-01-20 20:52 ` [gentoo-user] " Dale
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=CAE1pOi0+aQHayQqtvGWg673doAXJnDaQSujX6hGpHdNJojWKvg@mail.gmail.com \
--to=hilco.wijbenga@gmail.com \
--cc=gentoo-user@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