From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Managing multiple systems with identical hardware
Date: Fri, 27 Sep 2013 07:34:46 +0200 [thread overview]
Message-ID: <524518F6.9050903@gmail.com> (raw)
In-Reply-To: <52450AB6.3010900@gentoo.org>
On 27/09/2013 06:33, Johann Schmitz wrote:
> Hi Alan,
>
> On 26.09.2013 22:42, Alan McKinnon wrote:
>> You will break things horribly and will curse the day you tried.
>> Basically, puppet and portage will get in each other's way and clobber
>> each other. Puppet has no concept of USE flags worth a damn, cannot
>> determine in advance what an ebuild will provide and the whole thing
>> breaks puppet's 100% deterministic model.
>>
>> Puppet is designed to work awesomely well with binary distros, that is
>> where it excels. Keep within those constraints. Same goes for chef,
>> cfengine and various others things that accomplish the same end.
>
> Did you try to combine one of these solutions with portage's binary
> package feature? With --usepkgonly gentoo is more or less a binary
> distro. I'm thinking of using a single use flag set for 20+ Gentoo
> servers to get rid of compiling large packages in the live environment.
binpkgs don't turn gentoo into a binary distro, they turn it into
something resembling a Unix from the 90s with pkgadd - using dumb
tarballs with no metadata and no room to make choices. Puppet fails at
that as the intelligence cannot happen in puppet, it has to happen in
portage. If the binpkg doesn't match what package.* says, puppet is
stuck and portage falls back to building locally. The result is worse
than the worst binary distro.
By all means use a central use set, it's what I do for my dev VMs and it
works out well for me. Just remember to run emerge on each machine
individually.
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2013-09-27 5:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 21:18 [gentoo-user] Managing multiple systems with identical hardware Grant
2013-09-25 21:42 ` Alan McKinnon
2013-09-26 9:08 ` Grant
2013-09-26 20:42 ` Alan McKinnon
2013-09-27 4:33 ` Johann Schmitz
2013-09-27 5:34 ` Alan McKinnon [this message]
2013-09-27 10:37 ` Grant
2013-09-27 19:44 ` Alan McKinnon
2013-09-27 20:30 ` [gentoo-user] " James
2013-09-29 18:36 ` Grant
2013-09-29 20:39 ` Alan McKinnon
2013-09-29 18:31 ` [gentoo-user] " Grant
2013-09-29 19:06 ` Neil Bothwick
2013-09-29 20:57 ` Alan McKinnon
2013-09-30 17:31 ` Grant
2013-09-30 19:28 ` thegeezer
2013-09-30 19:31 ` Alan McKinnon
2013-09-30 19:53 ` Frank Steinmetzger
2013-10-01 6:19 ` Grant
2013-10-01 14:04 ` Michael Orlitzky
2013-10-01 15:00 ` Neil Bothwick
2013-09-30 21:02 ` Neil Bothwick
2013-10-01 6:26 ` Grant
2013-10-01 6:07 ` Grant
2013-10-01 6:20 ` Alan McKinnon
2013-10-02 18:54 ` Grant
2013-12-12 23:54 ` Grant
2013-12-13 0:16 ` Poison BL.
2013-12-13 0:34 ` wraeth
2013-12-13 2:06 ` Grant
2013-12-13 9:12 ` Neil Bothwick
2013-12-13 1:49 ` Grant
2013-12-13 7:57 ` Alan McKinnon
2013-12-13 9:18 ` Neil Bothwick
2013-12-13 7:52 ` Alan McKinnon
2013-10-01 7:43 ` Neil Bothwick
2013-10-01 18:37 ` joost
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=524518F6.9050903@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@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