eselect-repository vs layman, need some details

[UlvHare]

Having problem with update today (https://forums.gentoo.org/viewtopic-t-1112670.html) I'm suddenly found out an alternative for layman - eselect-repository. But I cannot understand from Wiki, is it suitable for my situation. I'm using only 2 overlays: palemoon and local (/usr/local/portage, it exists only there and on backup disk). How can I add my local overlay to eselect-repository if possible? Is eselect-repository better than layman in such case?

[Ionen]

eselect-repository is essentially a wrapper to edit /etc/portage/repos.conf while (optionally) using the database of known overlays. Once that's done, any of emerge --sync / eix-sync / emaint etc... will start sync'ing those overlays alongside ::gentoo without further actions.

Alternatively, you can edit repos.conf yourself and control everything. The two above links should have most answers.
Edit: adding a local overlay to repos.conf is just 3 lines of config, see [localrepo] example. You can probably add it with eselect-repos too but I never tried

[UlvHare]

Thank you very much!
I have my local overlay in repos.conf already (some years ago, manually), but I had no doubt that layman is necessary to delegate overlays to eix-sync.

[fpemud]

eselect-repository can enable or disable a overlay as a whole.
Does eselect-repository have a enable-one-overlay-package function?
I think this would be a very useful function. Sometimes I only need one package (and it's deps) from an overlay.

[fedeliallalinea]

You can done this masking all packages from an overlay and unmask only those you need

[fpemud]

Manual operation is really tedious.
I wish layman or eselect-repository could implement these functions (enable-package/disable-package) as subcommands.

[fedeliallalinea]

Manual operation is really tedious.

Two command

Code: Select all

# echo '*/*::<overlay_name>' >> /etc/portage/package.mask
# echo '<cat>/<pkg>::<overlay_name>' >> /etc/portage/package.unmask