From: Toby Dickenson <tdickenson@devmail.geminidataloggers.co.uk>
To: "Riyad Kalla" <rsk@u.arizona.edu>, <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Release/Stable/Dev
Date: Wed, 20 Nov 2002 16:00:08 +0000 [thread overview]
Message-ID: <200211201600.08126.tdickenson@devmail.geminidataloggers.co.uk> (raw)
In-Reply-To: <002a01c290a3$2cd39d10$d628c480@rsk>
On Wednesday 20 November 2002 2:43 pm, Riyad Kalla wrote:
> This is more of a "how does this work" question:
>
> I notice so much activity on this list all the time with new packages
> and new ideas and new ebuilds, etc. etc... And I realize that the idea
> of a "release version" of Gentoo isn't the same as RedHat or Mandrake
> where there is a snapshot in time of a code base that is deemed a
> "release", its sort of this every-growing and changing repository of
> ebuilds.
>
> This is cool and everything, but it also makes it hard for people that
> need to get a "stable release quality" version to say slap on a
> production server... So for example, if I download Gentoo 1.4, and
> install it today, and my coworker downloads gentoo 1.4 and installs it 2
> weeks from now, we *might* have different systems cause when he emerged
> his original system, some of the packages had changed... (is this an
> accurate assessment?)
>
> How do I combat this? Say if I'm interested in a rock-solid snapshot of
> Gentoo without going through an ungodly amount of administrative setup
> and mirroring of the snapshot etc.?
The administrative overhead of doing this is small, and well worth the effort.
1. use rsync to take a copy of today's portage into a directory on one of your
servers. In this example I use /var/mirror/portage-stable.
2. create an /etc/rsync.d like the one below, and run rsync --deamon.
3. on every other stable server, change their make.conf to include:
SYNC="rsync://my.local.rsync.server/portage-stable
4. you probably also should set up a distfiles archive, so that you can still
install old things when the real portage has moved on.
5. I am still uncertain about the best way to handle critical updates to these
stable systems. Currently I have a seperate rsync mirror which contains a
PORTDIR_OVERLAY directory. That contains copies of ebuilds from the real
portage.
my /etc/rsync.d is:
pid file = /var/run/rsyncd.pid
timeout = 150
[gentoo-portage-stable]
path = /var/mirror/portage
comment = Gentoo Portage Tree
[gentoo-portage]
path = /var/mirror/portage-stable
comment = Stable Snapshot of Gentoo Portage Tree
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2002-11-20 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 14:43 [gentoo-dev] Release/Stable/Dev Riyad Kalla
2002-11-20 15:20 ` Mark Constable
2002-11-20 16:00 ` Toby Dickenson [this message]
2002-11-20 16:21 ` Chad Huneycutt
2002-11-20 16:33 ` Toby Dickenson
2002-11-20 16:42 ` Chad Huneycutt
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=200211201600.08126.tdickenson@devmail.geminidataloggers.co.uk \
--to=tdickenson@devmail.geminidataloggers.co.uk \
--cc=gentoo-dev@gentoo.org \
--cc=rsk@u.arizona.edu \
--cc=tdickenson@geminidataloggers.com \
/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