public inbox for gentoo-cluster@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philipp Riegger <lists@anderedomain.de>
To: gentoo-cluster@lists.gentoo.org
Subject: Re: [gentoo-cluster] examples of (large) Gentoo clusters
Date: Sat, 2 Dec 2006 21:51:28 +0200	[thread overview]
Message-ID: <07F1B6B2-BCEA-47AE-92EE-954ABAA0BD51@anderedomain.de> (raw)
In-Reply-To: <200612021757.kB2HvgMn004007@ece06.nas.nasa.gov>


On Dec 2, 2006, at 7:57 PM, Bryan Green wrote:

> I'd very interested in the different approaches here.  I had  
> thought about a
> static portage tree, but that left the problem of getting needed  
> updates,
> especially GLSA's.  Your suggested approach sounds very interesting.
> How big of an extra administrative burden does that create?   
> Maintaining our
> own version controlled portage tree might be a hard sell.  Thanks  
> for the
> script - I'll take a look at it.  Is there any documentation out  
> there about
> a static portage tree?

On gentoo-dev there is a discussion going on about a sort of gentoo  
stable tree. Chris Gianelloni (if i remember it correctly) stated  
that he wanted to create a 2007.1 tree with the 2007.1 release and  
only put security fixes and required packages of security fixes in...

I did not make it clear: He wants to take a snapshot of the tree when  
2007.1 will be released and then like above.

_But_ there are like 50 more unread messages of the thread in my  
mailbox, so might be this is not true anymore. Look at the gentoo-dev  
archives.

Philipp
-- 
gentoo-cluster@gentoo.org mailing list



  reply	other threads:[~2006-12-02 19:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01 23:16 [gentoo-cluster] examples of (large) Gentoo clusters Bryan Green
2006-12-02  3:48 ` Donnie Berkholz
2006-12-02 13:54   ` Hanni Ali
2006-12-02 18:12     ` Bryan Green
2006-12-02 17:57   ` Bryan Green
2006-12-02 19:51     ` Philipp Riegger [this message]
2006-12-03  3:49     ` Donnie Berkholz
2006-12-04 18:15       ` Bryan Green
2006-12-04 20:53         ` Donnie Berkholz
2006-12-04 22:35           ` Hanni Ali
2006-12-04 23:00           ` Bryan Green
2006-12-04 23:55             ` Daniel van Ham Colchete
2006-12-05  3:55               ` Donnie Berkholz
2006-12-05 13:18               ` John R. Dunning
2006-12-05 16:25                 ` Bryan Green
2006-12-05 21:15                 ` Daniel van Ham Colchete
2006-12-05 21:22                   ` Bryan Green
2006-12-05 21:28                   ` John R. Dunning
2006-12-07  0:33                     ` Bryan Green
2006-12-07 13:12                       ` John R. Dunning
2006-12-08  3:56                         ` Bryan Green
2006-12-08 14:18                           ` John R. Dunning
2006-12-08 17:15                             ` Bryan Green
2006-12-11 13:38                               ` John R. Dunning
2006-12-08 18:29                             ` Donnie Berkholz
2006-12-08 18:52                               ` Bryan Green
2006-12-08 19:10                               ` John R. Dunning
2006-12-11 19:44                             ` Bryan Green
2006-12-02 14:40 ` Nick Anderson

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=07F1B6B2-BCEA-47AE-92EE-954ABAA0BD51@anderedomain.de \
    --to=lists@anderedomain.de \
    --cc=gentoo-cluster@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