From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: USE flag question (not total newbie)
Date: Tue, 29 Nov 2016 08:35:31 +0000 [thread overview]
Message-ID: <20161129083531.58716c50@digimed.co.uk> (raw)
In-Reply-To: <20161129020950.15561.30AFAB04@matica.foolinux.mooo.com>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
On Mon, 28 Nov 2016 18:15:06 -0800, Ian Zimmerman wrote:
> > No, I believe it means that the _option_ to enable or disable qt4 has
> > been removed.
>
> Well - notice the 'R'. So the package (or at least the version, see
> below) has not been changed since last time.
The version hasn't changed but the USE flags have, hence the rebuild.
Probably because you are using either --newuse or --changed-use.
> Is it possible for the ebuild to change (in particular, for USE flags to
> be removed) without a change in version number?
Yes, ebuilds can be, and are, changed without a revision bump under some
circumstances. Hence the presence of the above flags for emerge. I prefer
--changed-use since it is less intrusive, only rebuilding when the
changed USE flag actually makes a difference.
--
Neil Bothwick
Top Oxymorons Number 15: Extinct Life
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2016-11-29 8:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 1:34 [gentoo-user] USE flag question (not total newbie) Ian Zimmerman
2016-11-29 1:55 ` Stroller
2016-11-29 2:15 ` [gentoo-user] " Ian Zimmerman
2016-11-29 8:35 ` Neil Bothwick [this message]
2016-11-29 9:51 ` Alan McKinnon
2016-11-29 4:12 ` [gentoo-user] " J. Roeleveld
2016-11-29 4:59 ` [gentoo-user] " Ian Zimmerman
2016-11-29 8:37 ` Neil Bothwick
2016-11-29 12:26 ` Peter Humphrey
2016-11-29 12:48 ` Alan McKinnon
2016-11-29 18:36 ` Ian Zimmerman
2016-11-30 5:44 ` J. Roeleveld
2016-11-30 8:31 ` Ian Zimmerman
2016-11-30 9:40 ` J. Roeleveld
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=20161129083531.58716c50@digimed.co.uk \
--to=neil@digimed.co.uk \
--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