Summary: | Portage should have a dependancy on mktemp/coreutiles | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Tres 'RiverRat' Melton <RiverRat> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tres 'RiverRat' Melton
2008-05-11 11:08:26 UTC
(In reply to comment #0) > I removed mktemp and then did an emerge system knowing that coreutils would > get upgraded and the new version would include the new mktemp. After removing mktemp you should immediately upgrade coreutils. Otherwise many packages might fail to build. Portage doesn't need mktemp. mktemp is used by xmlto, which is used when Portage is being installed with USE="doc". The solution was easy enough: emerge -av coreutils Then emerge -av system As confirmed by Arfrever in the preceding comment. My point was that portage should maybe help people through such things. mktemp is part of system and always will be |