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