From: Andreas Fink <finkandreas@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What does emerge status R mean?
Date: Sun, 16 May 2021 12:53:22 +0200 [thread overview]
Message-ID: <20210516125322.230b4838@anfink-laptop> (raw)
In-Reply-To: <c7e4fac8-b4de-abed-bade-5369f2baf187@web.de>
On Sun, 16 May 2021 12:49:26 +0200
n952162 <n952162@web.de> wrote:
> On 5/16/21 11:28 AM, Neil Bothwick wrote:
> > On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote:
> >
> >>>> There are no use flags defined for any of the packages I did a random
> >>>> check for, either on the server or the client. I am worried that it
> >>>> is as you say: that the ebuild has a change of USE flags, which, of
> >>>> course, has nothing to do with me, the user.
> >>> As already stated, any USE flag changes would appear in the emerge
> >>> output, this is most likely caused by --changed-deps. Try with
> >>> --changed-use but without --changed-deps to see.
> >>>
> >>>
> >> I have introduced that into my build script. But, if it's as you say,
> >> the one is a subset of the other, it should have no effect on the
> >> output, right?
> >>
> > --changed-use is a subset of --newuse. --changed-deps is separate.
> >
> >
> Ah, I oversaw that.
>
> Ah. why would I want to have --changed-deps anyway? That suddenly seems
> silly.
>
> It's unfortunate, if there's no explanatory display if a package got
> disqualified for that reason.
>
>
If you want to have a binhost, then --changed-deps will become
"necessary" at some point. Let me draw you a picture, where a binhost
would fail to provide the correct package:
- Binhost builds on day 1 package XYZ
- computer that would merge with packages from binhost is NOT updated
- the dependencies are changed on day 2
- Binhost does NOT rebuild, because you do not have --changed-deps
enabled on day 2
- Computer that merges from the binhost is updated on day 2 but will
NOT use the binary package from binhost, because the dependencies do
not match
There are flags to ignore dependency mismatches, but the default would
just not use the binary package.
Cheers
Andreas
next prev parent reply other threads:[~2021-05-16 10:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 9:54 [gentoo-user] What does emerge status R mean? n952162
2021-05-14 16:07 ` Jack
2021-05-16 9:11 ` n952162
2021-05-16 9:23 ` Neil Bothwick
2021-05-16 9:26 ` n952162
2021-05-16 9:28 ` Neil Bothwick
2021-05-16 10:49 ` n952162
2021-05-16 10:53 ` Andreas Fink [this message]
2021-05-16 11:14 ` n952162
2021-05-16 12:24 ` Andreas Fink
2021-05-16 13:10 ` n952162
2021-05-16 10:59 ` n952162
2021-05-14 18:11 ` Neil Bothwick
2021-05-16 9:21 ` n952162
2021-05-16 16:11 ` Neil Bothwick
2021-05-15 5:24 ` Dan Egli
2021-05-16 9:23 ` n952162
2021-05-16 10:01 ` Dale
2021-05-16 10:51 ` n952162
2021-05-16 11:02 ` Andreas Fink
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=20210516125322.230b4838@anfink-laptop \
--to=finkandreas@web.de \
--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