Plus!
n00b
Joined: 04 Mar 2008
Posts: 15
|
 Posted: Sat Apr 06, 2024 3:08 pm Post subject: Multiple REPOS_BASE for eselect-repository |
 |
|
I have a centralized storage of overlays located on the NFS share.
It consists of multiple overlay sets, and the directory structure looks like:
| Code: |
overlays-store/overlay-set1/overlay1-timestamp1
overlays-store/overlay-set1/overlay2-timestamp2
overlays-store/overlay-set2/overlay3-timestamp3
overlays-store/overlay-set2/overlay4-timestamp4
overlays-store/overlay-set2/overlay1-timestamp5
|
I have a separate layman.cfg file inside each overlays-store/overlay-set# directory with at least a "storage" variable override.
Also, the "overlays-store/overlay-set#" directory contains a "make.conf" file that appends overlay paths to $PORTAGE_OVERLAY.
On the client machine, I mount the NFS share from the central server and source the above-mentioned "make.conf" file in the /etc/portage/make.conf.
All management (add/remove/sync) of the overlays is performed on the central server with the layman tool.
Now I am trying to migrate to "eselect-repository" (since the app-portage/layman was masked).
I see that "eselect-repository" uses the /etc/eselect/repository.conf file.
How can I override it with a command line similar to the layman -c option?
The next question is how I can specify REPOS_BASE during an overlay sync.
Basically I can go without sync, since typically I create new "overlay-set" instead of synchronizing existing one to preserve history and to not break things. |
|
Portage & Programming
