Summary: | app-portage/eix-0.19.2:0: doesn't find obsolete entries in package.keywords | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Jeremy Olexa (darkside) (RETIRED) <darkside> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | martin, pchrist |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Toralf Förster
2010-04-27 08:25:18 UTC
You probably also have a line like e.g.
kde-base/solid:4.4
It is somehow a design decision that eix collects all entries in
/etc/portage/package.keywords
matching for one package and only checks whether the combined result has
redundancies. This is necessary, because subsequent lines can cancel the
result of earlier lines. For instance you can have something like
foo/bar amd64-linux
>=for/bar:2 -amd64-linux ~amd64
and so testing of the first line without knowledge of the latter line does
not really make sense.
I hope, it is clear now why the combination of both lines
=kde-base/solid-4.3.5-r1
kde-base/solid:4.4
is not considered as redundant: eix cannot distinguish it from the single line
kde-base/solid
In the particular case you describe, an individual testing of lines might
thus make sense, but I see no reasonable way to combine both (the possibility
to use -~x86 later just causes lots of trouble).
So I think, I will leave it as it is.
(In reply to comment #1) > You probably also have a line like e.g. > kde-base/solid:4.4 Yes - I overlooked the separate kde-4.4 file > So I think, I will leave it as it is. of course |