eix -D is great, however it would be nice to have also option/eixrc flag to list duplicate packages among several overlays(+portage tree), even if they don't collide on the same versions, just the packages. The most flexible way would prolly be to add eixrc variable named like DUPLICATE_IF with these possible values: versions_all (exact version match for portage/overlays, current behaviour, would become default) versions_overlays (exact version match only among overlays) packages_all (same package in portage / overlays) packages_overlays (same package only among overlays) thanks in advance if you consider that worth to do
For such 2x2 cases, two Boolean variables might be more natural. But actually, I think the versions/packages choice should be easier to change at runtime, i.e. through a different test option. The other - presumably more constant - choice might be controlled by variables (two different Boolean variables to allow independent defaults for the two cases). The corresponding change is now in the new svn trunk and will probably go into eix-0.6.1. Test it, and let me know what you think (or whether you found other bugs in the trunk).
Thanks, it seems to work fine here, have no other problems with trunk (except bug 142503). I also agree on how you implemented it. Just found this wording weird in man eix for -d: "Only match duplicated packages with duplicated packages" Should be something like "Only match duplicated packages" The man also doesn't make clear what is the default (true/false) but that seems to be problem of other true/false options as well. Something less related, I tried the --pipe option. Not really sure what it's good for (with genlop it's pretty obvious :), but it would be much more useful if it could mark also the version that's going to be installed in the version list and/or add some "Will install: %version" line below the "Installed: %version" line.
Thanks for the testing. The manpage is corrected now. > The man also doesn't make clear what is the default (true/false) but that > seems to be problem of other true/false options as well. Actually this is the case with *all* variables in the manpage, and probably it is better to not document the defaults, since people should not rely that they do not change. The --dump option can be used to display the defaults. > I tried the --pipe option. Not really sure what it's good for To be honest, I also don't know, but I found it in the TODO-file when I took the maintainership, so some people want it, and I decided to implement it. Actually, this option can parse more than only the emerge -pv output; this is documented now in the manpage. > It would be much more useful if it could mark also the version that's going > to be installed This is not easy to implement, because the packages data cannot be available during input parsing. Of course, one could store this for later... however, I am not sure whether this is worth all the trouble: As you said, this option is probably only good for nothing.
> but it would be much more useful if it could mark also the version I changed my mind. This is now implemented.
Seems to work, thanks.
we believe this is fixed with 0.6.2 thanks or reporting!
