public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ~amd64 - my experience so far...
Date: Tue, 13 Apr 2010 15:30:28 +0800	[thread overview]
Message-ID: <1271143828.8658.53.camel@rattus> (raw)
In-Reply-To: <201004130909.24144.alan.mckinnon@gmail.com>

On Tue, 2010-04-13 at 09:09 +0200, Alan McKinnon wrote:
> On Monday 12 April 2010 18:33:21 KH wrote:
> > Am 12.04.2010 14:57, schrieb Alan McKinnon:
> > 
> 
> So, in the rare case of a user who can discipline himself to say within the 
> limits you describe, your advice is fine. But that's a theoretical situation 
> :-) and the real one is quite different in my experience.
> 
> 

This is exactly how I manage a number of gentoo systems - only unmasking
versions I need.  Ive actually never done a ~ system :)

However, on the other side of the coin is the fact I have also never run
a completely stable system either because I have never been able to get
the task done a system was built for without at least a few unstable
packages.  For an extreme example, remember when X was masked for some
security problem leaving stable with no X windows system (think it was
back in the xfree86 days).  You will quite often find that when trying
to build even a basic system, you have to keyword a few packages or you
get nowhere.  And if its a complex 1000 pkg plus system, you are
definitely going to have problems.

One hint I can give for long term stability is to try and specify
versions (either with = or ~) rather than just an open keywording.
Otherwise it gets out of hand with many unmasked packages needed and
needing maintaining on upgrades.

BillK








  reply	other threads:[~2010-04-13  7:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 11:57 [gentoo-user] ~amd64 - my experience so far Mark Knecht
2010-04-12 12:00 ` Alan McKinnon
2010-04-12 12:29   ` Mark Knecht
2010-04-12 12:42     ` William Kenworthy
2010-04-12 12:56       ` Mark Knecht
2010-04-12 13:10       ` [gentoo-user] " Kerin Millar
2010-04-12 12:57     ` [gentoo-user] " Alan McKinnon
2010-04-12 16:33       ` KH
2010-04-13  7:09         ` Alan McKinnon
2010-04-13  7:30           ` William Kenworthy [this message]
2010-04-13 12:40             ` Mark Knecht
2010-04-13 15:12               ` Paul Hartman
2010-04-13 16:11                 ` Mark Knecht
2010-04-13 17:34                   ` Alex Schuster
2010-04-13 18:30                     ` Mark Knecht
2010-04-13 15:37               ` Paul Hartman
2010-04-12 14:01     ` Neil Bothwick
2010-04-12 12:14 ` Zeerak Mustafa Waseem
2010-04-12 12:35   ` Mark Knecht
2010-04-12 13:07     ` [gentoo-user] " walt
2010-04-12 18:44       ` Mark Knecht
2010-04-12 18:57         ` Paul Hartman
2010-04-12 19:02           ` Paul Hartman
2010-04-12 21:03           ` Mark Knecht
2010-04-12 21:14             ` Paul Hartman
2010-04-12 22:18               ` Mark Knecht
2010-04-12 19:02         ` Alex Schuster
2010-04-12 13:06 ` Kerin Millar
2010-04-12 15:45 ` [gentoo-user] " Paul Hartman
2010-04-12 18:30   ` Paul Hartman

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=1271143828.8658.53.camel@rattus \
    --to=billk@iinet.net.au \
    --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