This module provides a emerge wrapper that worksalike portage emerge but can use paludis and pkgcore infrastructure instead, making PM usage seemless to the user.
eselect is completely the wrong tool for this. It wasn't designed to do anything like what you're describing.
This is, frankly, stupid.
eselect should just manage to switch the implementation, the emerge wrapper won't be done as eselect (pretty much as the other wrappers)
Huh? So you're proposing a SoC project for an eselect module that manages symlinks? The kind of module that should take about ten minutes to write?
Given I hadn't a better place to put I picked this one to clarify the task has those 2 items: - 1 prepare wrappers for pkgcore and paludis - 2 prepare an eselect module to switch the emerge and sync configurations if feasible. - 3 do the same for emaint and friends.
Wrappers? Or clients?
Good point, both pkgcore and paludis have a defined api and can be used through a plethora of languages. Clients/applications is a better definition since you don't have to wrap requests and pass them to the pmerge or paludis binary.
(In reply to comment #3) > eselect should just manage to switch the implementation, We have app-admin/eselect-package-manager which sets the PACKAGE_MANAGER environment variable. This could be tested in any wrapper. > the emerge wrapper won't be done as eselect (pretty much as the other > wrappers) Eselect team is out of here. Reassigning to maintainer-wanted.
This doesn't really belong in maintainer-wanted@ *until* there's an actual thing to package.
