Joined: 22 Jan 2003
|Posted: Thu Oct 11, 2018 1:16 pm Post subject:
|From what I remember /etc/make.conf was the original position and portage will use that make.conf if it exists. Have not checked what happens if make.conf exists in both /etc/ and /etc/portage. As all my machines use a copy of the build server's /etc/portage and the build server uses a slightly different make.conf than the other machines it suites me fine leaving make.conf in /etc.
soe = standard operating environment
Each machine has it's own world file. In my local overlay (which is also synced to every machine) I have an ebuild where the DEPEND line lists everything to be installed. When that ebuild is installed on each machine it pulls in all the wanted packages. Doing this if I want to add or remove a package I edit 1 ebuild and let the change propagate. Not every install is identical but this makes sure the core set of packages is installed.
Another way would be to make a set then emerge -av @some-set instead of emerge -av dummy-package. Either way one command to install a predefined set of packages. Just had a quick play making a set in /etc/portage/sets/ and that was easy.
Beware the grue.