public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Emerge Problems...
Date: Tue, 1 Feb 2011 15:39:58 +0000	[thread overview]
Message-ID: <20110201153958.1d0f33b1@zaphod.digimed.co.uk> (raw)
In-Reply-To: <967886.14950.qm@web39307.mail.mud.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]

On Tue, 1 Feb 2011 05:48:32 -0800 (PST), BRM wrote:

> If the machine is not fast enough - mine is a PII 233 w/160 MB RAM,
> takes a while do to updates - then you really have to separate out what
> you are hosting from what you are using. Otherwise you end up in the
> situation that you have started one system update (or software
> install), have a build failure for whatever reason, and then can't
> complete the same one due to changes in the local copy of portage.

You can still use emerge -sync instead of a home brewed script. In make
conf, set SYNC to localhost, then in your cron job, do

SYNC="some gentoo rsync mirror" emerge --sync

> So, even if your system fell into the first situation - where it is
> fast enough 
> - then I would still recommend doing the little extra to run as the
> second situation. It's just far easier to maintain.

I've been using a single portage tree to serve a LAN and for use by the
host for years with no hint of any of the problems you suggest. I just
make sure the cron job on the server syncs earlier than the rest of the
LAN and everything is up to date.


-- 
Neil Bothwick

Politics: Poli (many) - tics (blood sucking parasites)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-02-01 16:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30  4:12 [gentoo-user] Emerge Problems BRM
2011-01-30  9:31 ` [gentoo-user] " Francesco Talamona
2011-01-30 12:03 ` [gentoo-user] " Neil Bothwick
2011-01-30 17:59   ` BRM
2011-01-31 11:35     ` Marc Joliet
2011-01-30 21:07 ` Nils Holland
2011-01-31 14:55   ` BRM
2011-01-31 20:35     ` [gentoo-user] " Francesco Talamona
2011-01-31 22:26       ` BRM
2011-02-02  1:04         ` Peter Humphrey
2011-01-31 22:43       ` Nils Holland
2011-02-01  0:13         ` Dale
2011-02-01 13:48           ` BRM
2011-02-01 15:39             ` Neil Bothwick [this message]
2011-02-01 17:20               ` Dale
2011-02-01 20:41                 ` Joshua Murphy
2011-02-02 21:18                   ` Nils Holland
2011-02-01 20:43                 ` BRM
2011-02-01 21:21                   ` Dale
2011-02-02  1:27                   ` Peter Humphrey
2011-02-02 17:29                     ` BRM
2011-02-01 21:35           ` Nils Holland
  -- strict thread matches above, loose matches on Subject: below --
2009-01-03 20:31 [gentoo-user] emerge problems James Stull
2009-01-04 11:35 ` pk
2009-01-05  0:48   ` James Stull
2009-01-05  0:55     ` [gentoo-user] " Nikos Chantziaras
2009-01-05  0:57       ` Nikos Chantziaras
2009-01-05 14:27         ` James Stull

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=20110201153958.1d0f33b1@zaphod.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