From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Managing multiple systems with identical hardware
Date: Sun, 29 Sep 2013 20:06:08 +0100 [thread overview]
Message-ID: <20130929200608.504f9cd6@digimed.co.uk> (raw)
In-Reply-To: <CAN0CFw1O-emn6qg3fdC7iDLsfM5oTn9p_ny95HEyUO-qtFHDaQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Sun, 29 Sep 2013 11:31:17 -0700, Grant wrote:
> > Personally, I wouldn't do the building and pushing on my own laptop,
> > that turns me inot the central server and updates only happen when I'm
> > in the office. I'd use a central build host and my laptop is just
> > another client. Not all that important really, the build host is just
> > an address from the client's point of view
>
> I don't think I'm making the connection here. The central server
> can't do any unattended building and pushing, correct? So I would
> need to be around either way I think.
If you ran the central server in a VM, you could have it run "emerge
--sync && emerge -uDN @world" from cron. You could do this without a VM,
but a VM allows you to take snapshots before each sync/build cycle, so
that you can roll back if an update breaks it.
--
Neil Bothwick
The severity of the itch is inversely proportional to the reach.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-09-29 19:06 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
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 [this message]
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=20130929200608.504f9cd6@digimed.co.uk \
--to=neil@digimed.co.uk \
--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