Paludis

[kirelagin]

I'd like to reopen this old feature request.

Probably things have changed since the original request, but anyway right now I can't see any difference between Paludis' and Portage's config formats.

Actually, what I did, I symlinked relevant directories from /etc/paludis to /etc/portage to get eix to see those files. It would be nice to teach eix to read Paludis' config, probably, depending on $PACKAGE_MANAGER.

[kirelagin]

Right, there is one issue that can't be worked around with symlinking: getting the list of overlays.

So to get the list of paludis repositories you have to go through /etc/paludis/repositories/*.conf and read location from each file. While somewhat different from portage, I think that's worth implementing, as it looks like portage is also moving in that direction: recent upgrade created /etc/portage/repos.conf on my laptop which is almost the same, just in a single file.

[vaeth]

Paludis is on the TODO list, but it seems I never find the time to do it.

Last time, I checked, user configuration formats were still rather different (repo-based instead of package-based, regular expressions etc.: Probably the current internal "mask lists" of eix are not sufficient for paludis; it might be a mere accident that you didn't use the full feature set). Especially support for eix -T ("eix-test-obsolete") seems to be rather cumbersome - probably it is better to write it separately for paludis (or not support it at all in "Paludis mode"). Moroever, also the /var/db/pkg format is not guaranteed to be the same (since it is only partially documented, one can only try...).

Anyway, this is not a reason to not start at least some basic support for paludis, although I am afraid that it can mean opening Pandora's box...

However, main obstacle for me is lack of time...

Patches are welcome.