-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paludis #2
Comments
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 |
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. |
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
.The text was updated successfully, but these errors were encountered: