Re: [gentoo-user] Curious emerge behaviour.

[Mike Williams <mike@gaima.co.uk>]

On Thursday 03 July 2008 06:40:17 Alan McKinnon wrote:
> > Anyone else having this particular problem? Is it a compatibility
> > issue with either coreutils or mktemp? I'm assuming removing the one
> > will eliminate it, but if it's a needed package I'd rather not chance
> > it. Any info on this one would be greatly appreciated.
>
> Pretty standrad blocker - been around for a while on ~arch.
>
> coreutils now provides what used to be in mktemp, so
>
> emerge -C mktemp ; emerge coreutils
>
> will sort it

However that will leave you without the mktemp binary while coreutils gets 
built. Unlikely to be a problem, unless a reboot happens in the middle, and 
still probably quite recoverable.

I've taken to making sure the collision-protect FEATURE is not set (which it 
isn't by default I believe), then removing the mktemp portage DB entry.
# mv /var/db/pkg/sys-apps/mktemp-1.5/ ~
With mktemp apparently not installed, no blocker exists, and you've still got 
the binary. Portage will complain when it comes to install the new coreutils, 
but just ignore it's complaint.

-- 
Mike Williams
-- 
gentoo-user@lists.gentoo.org mailing list