From: Michael Higgins <linux@evolone.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to "freeze" my Gentoo system
Date: Fri, 13 Mar 2009 10:24:07 -0700 [thread overview]
Message-ID: <20090313102407.24025395@lappy.evolone.org> (raw)
In-Reply-To: <20090312095105.29e56a13@krikkit.digimed.co.uk>
On Thu, 12 Mar 2009 09:51:05 +0000
Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 12 Mar 2009 10:13:30 +0200, Alan McKinnon wrote:
>
> > > Could he just not sync and call it a day? I suspect this is
> > > going to bite him one day tho. We know Gentoo likes to be
> > > updated fairly regular. I been around Gentoo for years and I
> > > don't think I would want to do this. I'm not sure how much
> > > experience the OP has tho.
No worries. If I break it, I get to keep the pieces...
> > Michael's been around a while, his name is familiar. He did say he
> > wants -rN updates so I take that to mean he wants bug fixes and
> > security updates but everything else to stay that same and
> > especially no potential ABI/API changes
>
> One potential problem is ebuilds disappearing from the portage tree as
> packages are updated, so it would be worth copying everything he uses
> (or the whole tree) into an overlay.
>
Thanks to you both for all the suggestions and caveats... I'll report back when I've done the script to populate package.mask with atoms *pre-*pended by '~'.
As one of you mentioned, it's not an unreasonable thing to want to "freeze" a system, but OTOH Gentoo does like regular updating.
If something drops from the tree, that's okay... My goal is, for packages I've unmasked for the architecture, that they don't keep being updated to the latest available, but eventually come into concordance with 'stable'.
Cheers,
--
|\ /| | | ~ ~
| \/ | |---| `|` ?
| |ichael | |iggins \^ /
michael.higgins[at]evolone[dot]org
next prev parent reply other threads:[~2009-03-13 17:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 20:40 [gentoo-user] How to "freeze" my Gentoo system Michael Higgins
2009-03-12 7:56 ` Alan McKinnon
2009-03-12 8:07 ` Dale
2009-03-12 8:13 ` Alan McKinnon
2009-03-12 8:26 ` Dale
2009-03-12 9:51 ` Neil Bothwick
2009-03-13 17:24 ` Michael Higgins [this message]
2009-03-13 19:43 ` Dale
2009-04-03 2:45 ` Mark David Dumlao
2009-04-03 23:56 ` Michael Higgins
2009-04-04 3:24 ` [gentoo-user] " ABCD
2009-03-12 9:48 ` [gentoo-user] " Neil Bothwick
2009-03-12 10:52 ` Alan McKinnon
2009-03-12 19:43 ` Neil Bothwick
2009-03-12 20:21 ` Alan McKinnon
2009-03-17 7:46 ` Sebastian Günther
2009-03-17 8:41 ` Neil Bothwick
2009-04-02 18:19 ` Michael Higgins
2009-03-13 23:55 ` Sean
2009-03-14 4:11 ` Beau Henderson
2009-03-14 9:38 ` Neil Bothwick
2009-03-18 9:57 ` Momesso Andrea
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=20090313102407.24025395@lappy.evolone.org \
--to=linux@evolone.org \
--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