Summary: | Support for /etc/portage/package.use in ufed | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Daniel Wirengren <dw> |
Component: | Tools | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | benkstein, stkabugs |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Daniel Wirengren
2004-05-27 15:37:38 UTC
I second that and I think there should also be a flag that no local flags are shown in ufed (or that be the default) and that ufed only changes them when called with a package name as argument as suggested by the OP. ufed is unmaintained and dying, it will be replaced by other tools soon that should have this functionality. Could you please point me to any of these other tools? I really liked ufed b/c it only had three dependencies (or so) and so was useable even before "emerge system". Thanks. The one that is in portage is app-portage/profuse, another one that will get in the future is http://www.cs.rpi.edu/~hays/pufed.py *** Bug 211163 has been marked as a duplicate of this bug. *** |