Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 31918 - shoudn't textutils/sh-utils/fileutils be blocked by coreutils?
Summary: shoudn't textutils/sh-utils/fileutils be blocked by coreutils?
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-24 08:01 UTC by Sven
Modified: 2004-06-29 11:51 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sven 2003-10-24 08:01:49 UTC
i don't think that it makes sense that textutils/sh-utils/fileutils and coreutils can be installed at once. so if i have coreutils installed, the other three packages should be blocked.
an alternative would be to intruduce dummy-ebuilds that simply depend on coreutils and install no files.
that would make life easier since textutils/sh-utils/fileutils would be uninstalled automatically if people update and there might still be some ebuilds that depend on sh-utils instead of coreutils (eclipse-sdk-2.1.1 ebuild for example).
Comment 1 Sven 2003-10-24 08:05:56 UTC
oops, sh-utils, textutils and fileutils are dummy-ebuilds already. silly
me. forget this bug-report.
Comment 2 Mr. Bones. (RETIRED) gentoo-dev 2004-06-28 23:51:53 UTC
*** Bug 55500 has been marked as a duplicate of this bug. ***
Comment 3 Timothy Weiand 2004-06-29 11:49:13 UTC
Question: Why is this bug marked resolved invalid?  I spent two hours rebuilding my MAC last night over this issue!

Just by making textutils, fileutils and sh-utils dummy ebuilds brings a hole different problem for systems that already have coreutils on them.  The upgrade process leave the machine in an unusable state.

I fail to see how this is resolved.
Comment 4 Timothy Weiand 2004-06-29 11:51:34 UTC
(please see bug #55500 to view my upgrade issues)