Gentoo Archives: gentoo-dev

From: Alexander Tsoy <alexander@××××.me>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Managing updates on many identical Gentoo systems
Date: Thu, 18 Jan 2018 22:53:50
Message-Id: 1516316010.2345.3.camel@tsoy.me
In Reply to: Re: [gentoo-dev] Managing updates on many identical Gentoo systems by Alexander Tsoy
1 В Пт, 19/01/2018 в 01:30 +0300, Alexander Tsoy пишет:
2 > В Чт, 18/01/2018 в 06:46 -0500, Anthony G. Basile пишет:
3 > > Hi everyone,
4 > >
5 > > I'm trying to design an update system for many identical Gentoo
6 > > systems.
7 > >  Using a binhost is obvious, but there are still problems with this
8 > > approach.
9 > >
10 > > Unless there's some magic I don't know about (and this is why I'm
11 > > sending this email) each machine still needs to have the portage
12 > > tree
13 > > installed locally (1.5 GB) or somehow mounted by a network
14 > > filesystem
15 > > (which is not practical if the machines are not on a local
16 > > network).
17 > > Furthermore, each machine would have to run emerge locally to do
18 > > the
19 > > calculation of what packages need updating.
20 >
21 > AFAIK each machine only needs "profiles" and "eclass" directories and
22 > not the full repo. eclass dir is needed because of the check below in
23 > ebuild.sh:
24 >
25 >
26 > inherit()
27 > ...
28 >     [[ -z ${location} ]] && die "${1}.eclass could not be found by
29 > inherit()"
30 >
31 > And this check actually should be skipped for binary packages. They
32 > are
33 > already contain full environment.
34
35 Oops. Forget the last part about inherit(). You need only profiles dir.
36 I experimented on a host with local overlay thus I got inherit
37 errors. :)