On Monday, 3 August 2020 23:01:07 BST Peter Humphrey wrote: > On Monday, 3 August 2020 20:15:45 BST Rich Freeman wrote: > > On Mon, Aug 3, 2020 at 3:01 PM Peter Humphrey <pe...@prh.myzen.co.uk> wrote: > > > On Monday, 3 August 2020 14:18:22 BST Rich Freeman wrote: > > > > Sounds like you want --usepkgonly y --binpkg-respect-use y (the first > > > > is the same as -K). At least, I think that is what you're getting at > > > > - I could be misunderstanding your goal. > > > > > > Not exactly. I'm finding that emerge -K installs every package whose > > > binpkg > > > exists, regardless of whether it's installed in the system already. > > > Emerge > > > -k doesn't. Neither of them takes any notice of what packages are > > > installed in the system, and I think they should. > > > > -k/K have nothing to do with package selection - just the use of > > binary packages. > > > > If you run emerge @core then anything in @core should get installed. > > Adding -K or -k will either allow or force the use of binary packages, > > but it shouldn't cause stuff that isn't in @core to get installed > > unless it is a dependency. > > That's exactly the problem. It does.
I mean, it does while in the chroot. Perhaps I'm setting something up wrongly. -- Regards, Peter.
