From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Binary package cruncher?
Date: Sun, 16 Nov 2008 12:05:53 +0200 [thread overview]
Message-ID: <200811161205.53841.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <491F09A2.7040506@gmail.com>
On Saturday 15 November 2008 19:40:50 Simon wrote:
> This is not super efficient, but the way I've thought it, should be
> simple to do... a simple gentoo hack so to speak. However, I'm wondering
> if anybody has suggestion for better ways to do this and if you could give
> me pointers to such projects. Also keep in mind that I really really want
> to update ALL my PCs with a single `emerge -uDN world` on the host, then
> copy new pkgs (using rsync or other) to the PCs and do an `emerge -k -uDN
> world` on them. Nothing more. (So unless your suggestion is simpler than
> my current (fully installed) setup, please tell me!)
I would build all that stuff in a chroot. The logic is that the your buildhost
system is not quite the same thing as the machine hosting the buildhost.
One thing you cannot get away from is that to build say X for your slow
hardware, it has to be done on a machine that has all X's build dependencies
fully installed and working. You might not want that on your production
server. Some fancy tricks with bind-mounts into the chroot would let you
share common stuff. Or, you could simply buy a bit more storage if you are
running out. It's cheap enough and if you've gone to this much trouble
already, some more storage would be minor
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2008-11-16 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 17:40 [gentoo-user] Binary package cruncher? Simon
2008-11-16 10:05 ` Alan McKinnon [this message]
2008-11-16 11:16 ` Peter Humphrey
2008-11-16 15:03 ` Simon
2008-11-16 14:59 ` Simon
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=200811161205.53841.alan.mckinnon@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