1 |
On Monday, 3 August 2020 23:01:07 BST Peter Humphrey wrote: |
2 |
> On Monday, 3 August 2020 20:15:45 BST Rich Freeman wrote: |
3 |
> > On Mon, Aug 3, 2020 at 3:01 PM Peter Humphrey <peter@××××××××××××.uk> |
4 |
wrote: |
5 |
> > > On Monday, 3 August 2020 14:18:22 BST Rich Freeman wrote: |
6 |
> > > > Sounds like you want --usepkgonly y --binpkg-respect-use y (the first |
7 |
> > > > is the same as -K). At least, I think that is what you're getting at |
8 |
> > > > - I could be misunderstanding your goal. |
9 |
> > > |
10 |
> > > Not exactly. I'm finding that emerge -K installs every package whose |
11 |
> > > binpkg |
12 |
> > > exists, regardless of whether it's installed in the system already. |
13 |
> > > Emerge |
14 |
> > > -k doesn't. Neither of them takes any notice of what packages are |
15 |
> > > installed in the system, and I think they should. |
16 |
> > |
17 |
> > -k/K have nothing to do with package selection - just the use of |
18 |
> > binary packages. |
19 |
> > |
20 |
> > If you run emerge @core then anything in @core should get installed. |
21 |
> > Adding -K or -k will either allow or force the use of binary packages, |
22 |
> > but it shouldn't cause stuff that isn't in @core to get installed |
23 |
> > unless it is a dependency. |
24 |
> |
25 |
> That's exactly the problem. It does. |
26 |
|
27 |
Well, I don't know what's going on. Today it all works perfectly. |
28 |
|
29 |
Sorry about the noise. |
30 |
|
31 |
-- |
32 |
Regards, |
33 |
Peter. |