Summary: | sys-apps/acl should warn people about the dangers of removing it | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ferret <ferret-bgo> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
ferret
2004-12-23 13:12:06 UTC
it wouldnt be useful at the end of the acl emerge ... they'd already shoot themselves in the foot ;) we can force a check in pkg_setup ... pkg_setup() { if built_with_use coreutils acl ; then eerror "Refusing to unmerge acl since coreutils was built with USE=acl" die "Dont shoot yourself, it hurts" fi } there doesnt seem to be a clean solution for this when doing `emerge -C acl`, the ebuild would be read from /var/db/pkg/ rather than an updated version i put in the tree ... so users would still be screwed even if i added this check there is no good way of figuring out if the user is upgrading and thus an older acl is being auto-cleaned, or if the user just did `emerge -C acl` ... both utilize the same functions and in the first case, we wouldnt want acl to bail |