public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stuart Herbert <stuart@gentoo.org>
To: Ron O'Hara <rono@sentuny.com.au>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Large scale deployments - and portage
Date: Sun, 17 Aug 2003 23:13:43 +0100	[thread overview]
Message-ID: <200308172313.43267.stuart@gentoo.org> (raw)
In-Reply-To: <3F3FFCFF.2080804@sentuny.com.au>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1567 bytes --]

Hi Ron,

On Sunday 17 August 2003 11:09 pm, Ron O'Hara wrote:
> If it were possible to 'tag' the portage tree with labels at regular
> intervals, and and do an 'emerge sync' with a nominated 'tag' - then you
> would have the equivelant of the fixed points that other distributions
> have when they cut a release CD.

It's an interesting idea ;-)

You might want to have a look at running your own (internal) rsync mirror for 
your Gentoo boxes - and your own (internal) distfiles mirror too.  This gives 
you complete control over what ebuilds your many Gentoo machines will get, 
and ensures that you can roll out software long after it has been removed 
from Gentoo's portage (we delete 'old' files all the time, when we believe 
they're obsolete, which really screws up consistency across a large 
deployment.  However, with your own internal mirror, you can keep these 
ebuilds and their distfiles around long after Gentoo has dropped them!)

Tbh, it's a hack, rather than a nice solid server/client enterprise-ready 
Portage solution, but it's one that does work.

Best regards,
Stu
-- 
Stuart Herbert                                              stuart@gentoo.org
Gentoo Developer                                       http://www.gentoo.org/
Beta packages for download            http://dev.gentoo.org/~stuart/packages/
Come and meet me in March 2004                 http://www.phparch.com/cruise/

GnuGP key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319  C549 0C2F 80BA F9AF C57C
--

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-17 22:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-17 22:09 [gentoo-dev] Large scale deployments - and portage Ron O'Hara
2003-08-17 22:13 ` Stuart Herbert [this message]
2003-08-17 23:27   ` Ron O'Hara
2003-08-18  0:22     ` Matt Thrailkill
2003-08-18 14:14       ` Stuart Herbert
2003-08-17 23:17 ` Robin H. Johnson
2003-08-17 23:37   ` Don Seiler
2003-08-18  8:24   ` Paul de Vrieze
2003-08-18  9:38     ` Robin H. Johnson
     [not found] ` <200308181026.44148.chris.rs@xtra.co.nz>
2003-08-18  0:34   ` Ron O'Hara
2003-08-18  8:38     ` Paul de Vrieze
2003-08-18  0:42 ` Brian Jackson
2003-08-18 14:45   ` Stuart Bouyer

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=200308172313.43267.stuart@gentoo.org \
    --to=stuart@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=rono@sentuny.com.au \
    /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