public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Vermeulen <svermeulen@siphos.be>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: emerge snapshots
Date: Thu, 26 Jan 2006 18:00:40 +0100	[thread overview]
Message-ID: <20060126170040.GG7201@gentoo.org> (raw)
In-Reply-To: <43D66006.4090504@thinrope.net>

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

On Wed, Jan 25, 2006 at 02:12:38AM +0900, Kalin KOZHUHAROV wrote:
> r100
> emerge foo
> r101
> emerge --unmerge foo
> r102

You're like asking to put your entire system under a versioning system
control. Sounds like fun, but also like a lot of diskspace usage on your
versioning server.

$ ${VCTOOL} commit --label=r100 --recursive /
$ emerge foo
$ ${VCTOOL} commit --label=r101 --recursive /
...
$ ${VCTOOL} checkout --label=r100 --recursive /

Using the FEATURES="buildpkg" helps a lot, especially if you also take
snapshots of your portage tree (since any breakage due to an "emerge -uDN
world" can hopefully be fixed by restoring the backup portage tree and run
"emerge -uDN world" again).

If you then put your configuration files under versioning control, you
should be set.

Wkr,
      Sven Vermeulen

-- 
  Gentoo Foundation Trustee          |  http://foundation.gentoo.org
  Gentoo Council Member  

  The Gentoo Project   <<< http://www.gentoo.org >>>

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

  parent reply	other threads:[~2006-01-26 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24 17:12 [gentoo-dev] RFC: emerge snapshots Kalin KOZHUHAROV
2006-01-24 18:00 ` Marius Mauch
2006-01-24 18:36 ` Wernfried Haas
2006-01-24 18:54   ` Re[2]: " Jakub Moc
2006-01-24 22:45   ` A. Khattri
2006-01-24 23:24     ` Francesco Riosa
2006-01-24 23:27       ` A. Khattri
2006-01-26 17:00 ` Sven Vermeulen [this message]
2006-01-27 23:08   ` [gentoo-dev] " Duncan
2006-01-27 23:31     ` Stephen Bennett
2006-01-28  1:47       ` [gentoo-dev] " Duncan
2006-01-28  2:27         ` Marcelo Góes

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=20060126170040.GG7201@gentoo.org \
    --to=svermeulen@siphos.be \
    --cc=gentoo-dev@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