On Sun, 16 May 2021 12:49:26 +0200 n952162 <n952...@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
