Vaeth schrieb:
> Neil Bothwick wrote:
>>> On Sun, 13 Apr 2008 14:02:38 +0200, Daniel Pielmeier wrote:
>>>
>>> Redundant is where the package is still available but the /etc/portage.*
>>> entry is no longer needed. e.g. you have "dev-lib/foobar-1.1 ~x86" in
>>> package.keyworkd but it is now stable.
>> Sounds reasonable, thanks!
>
> There are much more types of redundancies. E.g. if you marked it twice
> or with two different keywords etc. Use the REDUNDANT_IF_* variables
> (described on the eix manpage) to tell eix-test-obsolete in detail what
> types _you_ do consider as redundant.

Already read about this, now I think I fully understand it!

>>> Btw: eix-test-obsolete can not check for obsolete use-flags at the
>>> moment?
>
> eix does not have support for useflags at all (except for some very
> primitive cases and checks).
>
>> I wonder when there will be one single tool [...]
>> cleaning /etc/portage/
>
> I think there will never be a convenient tool, because there are too
> many cases: What somebody considers as obsolete (e.g. an ** unmasking
> when meanwhile ~x86 is available) is a natural entry for another person.
> IMHO, except for useflags, eix-test-obsolete cannot much be improved
> for such a task. In new eix versions you can even provide a file for
> packages for which you do *not* want to see warnings (e.g. if you *know*
> that you will always want the ~x86 version of that package, you will
> not get any warnings if the highest version is stable).

Thank you Martin this is very useful information! I always wondered if
the output could be suppressed for special packages.

I also see now that taking care of /etc/portage/ is a very difficult job!

You are thinking about implementing better support for use-flags?

Regards,

Daniel
--
gentoo-user@(protected)