[gentoo-user] Emerge -K ignoring new packages

[Peter Humphrey]

Hello list,

Now that I have my NFS set up (with help - thanks) the next problem is that,
having new packages built by my workstation over NFS, emerge on the tiny box
is ignoring all those new packages. And yes, I have checked that they do
exist, and in the right place: /var/cache/packages/ .

The man page says that any new package will cause a remerge, so what has
tripped me up this time?

[Vitaliy Perekhovy]

Post by Peter Humphrey
Hello list,
Now that I have my NFS set up (with help - thanks) the next problem is that,
having new packages built by my workstation over NFS, emerge on the tiny box
is ignoring all those new packages. And yes, I have checked that they do
exist, and in the right place: /var/cache/packages/ .
The man page says that any new package will cause a remerge, so what has
tripped me up this time?
--
Regards,
Peter.

Default location for binary packages is /var/cache/binpkgs/

[Wols Lists]

Post by Vitaliy Perekhovy

Post by Peter Humphrey
Hello list,
Now that I have my NFS set up (with help - thanks) the next problem is that,
having new packages built by my workstation over NFS, emerge on the tiny box
is ignoring all those new packages. And yes, I have checked that they do
exist, and in the right place: /var/cache/packages/ .
The man page says that any new package will cause a remerge, so what has
tripped me up this time?
--
Regards,
Peter.

Default location for binary packages is /var/cache/binpkgs/

Can't remember what I did, but the first thing to check is you're using
the same make flags (unless of course, you're sharing /etc/portage).

Then I seem to remember using -bK or something like that. So the command
I'm giving emerge is "use a binary if you can find it, otherwise build it".

Because I might emerge packages on either machine, that worked great for
me. And I actually usually emerged stuff on the slower machine, because
it was more reliable ... :-)

Cheers,
Wol

[Peter Humphrey]

Post by Vitaliy Perekhovy

Post by Peter Humphrey
Hello list,
Now that I have my NFS set up (with help - thanks) the next problem is
that, having new packages built by my workstation over NFS, emerge on the
tiny box is ignoring all those new packages. And yes, I have checked that
they do exist, and in the right place: /var/cache/packages/ .
The man page says that any new package will cause a remerge, so what has
tripped me up this time?

Default location for binary packages is /var/cache/binpkgs/

Oh? When did that change?

[Neil Bothwick]

Post by Peter Humphrey

Post by Vitaliy Perekhovy
Default location for binary packages is /var/cache/binpkgs/

Oh? When did that change?

It may not have on your system. To check the location, run

portageq pkgdir

[Peter Humphrey]

Post by Neil Bothwick

Post by Peter Humphrey

Post by Vitaliy Perekhovy
Default location for binary packages is /var/cache/binpkgs/

Oh? When did that change?

It may not have on your system. To check the location, run
portageq pkgdir

I know where it is because I set it to the recommended place when portage was
moved out of /usr. I just wondered when, and why, it had been changed. It will
stay where it is, here, if only because 'binpkgs' is harder to type than
'packages'.