From: Alexander Tsoy <alexander@tsoy.me>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Managing updates on many identical Gentoo systems
Date: Fri, 19 Jan 2018 01:30:56 +0300 [thread overview]
Message-ID: <1516314656.2345.1.camel@tsoy.me> (raw)
In-Reply-To: <2686de8e-334c-084b-4828-6109b10dd536@gentoo.org>
В Чт, 18/01/2018 в 06:46 -0500, Anthony G. Basile пишет:
> Hi everyone,
>
> I'm trying to design an update system for many identical Gentoo
> systems.
> Using a binhost is obvious, but there are still problems with this
> approach.
>
> Unless there's some magic I don't know about (and this is why I'm
> sending this email) each machine still needs to have the portage tree
> installed locally (1.5 GB) or somehow mounted by a network filesystem
> (which is not practical if the machines are not on a local network).
> Furthermore, each machine would have to run emerge locally to do the
> calculation of what packages need updating.
AFAIK each machine only needs "profiles" and "eclass" directories and
not the full repo. eclass dir is needed because of the check below in
ebuild.sh:
inherit()
...
[[ -z ${location} ]] && die "${1}.eclass could not be found by
inherit()"
And this check actually should be skipped for binary packages. They are
already contain full environment.
next prev parent reply other threads:[~2018-01-18 22:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 11:46 [gentoo-dev] Managing updates on many identical Gentoo systems Anthony G. Basile
2018-01-18 12:00 ` Joakim Tjernlund
2018-01-18 12:34 ` Lars Wendler
2018-01-18 19:22 ` NP-Hardass
2018-01-18 12:42 ` Martin Gysel
2018-01-18 15:36 ` [gentoo-dev] " Duncan
2018-01-18 22:13 ` Bill Kenworthy
2018-01-19 14:45 ` Alec Warner
2018-01-19 15:03 ` Anthony G. Basile
2018-01-19 18:13 ` Zac Medico
2018-01-20 15:34 ` Anthony G. Basile
2018-01-20 21:48 ` Zac Medico
2018-01-18 16:13 ` [gentoo-dev] " Alec Warner
2018-01-18 23:01 ` Zac Medico
2018-01-18 22:30 ` Alexander Tsoy [this message]
2018-01-18 22:53 ` Alexander Tsoy
2018-01-18 23:00 ` R0b0t1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1516314656.2345.1.camel@tsoy.me \
--to=alexander@tsoy.me \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox