public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: xorg-server-1.5 update/old kernel+old fglrx
Date: Wed, 24 Jun 2009 03:16:48 +0300	[thread overview]
Message-ID: <h1rr9f$hm0$1@ger.gmane.org> (raw)
In-Reply-To: <5bdc1c8b0906231706s3c140069rdbb9822e9b29699f@mail.gmail.com>

On 06/24/2009 03:06 AM, Mark Knecht wrote:
>[...]
> Am I hosed again? Did updating portage break my machine by removing
> what I was just using:
> [...]
>
> Is xorg-server-1.1.1 completely gone and I'm hosed? I'm not finding it
> on my my machine. The only variations on that theme seem to be in
> /var/db/pkg. No tar files, just other programming junk.
>
> I absolutely HATE this about portage. Update your machine just
> thinking about trying a new piece of software and then find you cannot
> immediately go back. Gentoo was supposed to be about choice. Seems
> it's not about my choice anymore. Bummer.

I hate to say this, but if you have a machine that you don't keep up to 
date by doing full updates at least each month or two, then Gentoo is 
*not* for you because Gentoo simply lacks the notion of "stable". 
"Stable" refers to package versions, not system stability.  Gentoo is 
never "stable" in that sense like other distros that offer "stable" 
releases.  Something like Debian stable should be more appropriate and 
far more easier to keep operational for machines like that.




  reply	other threads:[~2009-06-24  0:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 23:20 [gentoo-user] xorg-server-1.5 update/old kernel+old fglrx Mark Knecht
2009-06-23 23:27 ` [gentoo-user] " Nikos Chantziaras
2009-06-23 23:40   ` Mark Knecht
2009-06-23 23:53     ` Mark Knecht
2009-06-24  0:06       ` Mark Knecht
2009-06-24  0:16         ` Nikos Chantziaras [this message]
2009-06-24  0:27           ` Mark Knecht
2009-06-24  0:33             ` Nikos Chantziaras
2009-06-24  0:42               ` Mark Knecht
2009-06-24  1:32                 ` Neil Bothwick
2009-06-24  3:13                   ` Mark Knecht
2009-06-24  5:55                     ` Dale
2009-06-24  0:29         ` Nikos Chantziaras
2009-06-24  0:37           ` Mark Knecht
2009-06-24  1:46             ` Dale
2009-06-24  1:14         ` Keith Dart
2009-06-24  1:28         ` Neil Bothwick
2009-06-24  1:42           ` Mark Knecht
2009-06-24  7:46             ` Neil Bothwick
2009-06-24 20:17               ` Mark Knecht
2009-06-24 20:29                 ` Neil Bothwick
2009-06-24 20:32                 ` Alan McKinnon
2009-06-25  0:08                 ` Adam Carter
2009-06-25  0:46                   ` Mark Knecht
2009-06-25  0:59                     ` Nikos Chantziaras
2009-06-25  1:25                       ` Mark Knecht
2009-06-25  1:04                     ` Adam Carter
2009-06-25  1:07                       ` Nikos Chantziaras
2009-06-25  1:15                         ` Adam Carter
2009-06-25  1:27                       ` Mark Knecht
2009-06-25  1:51                         ` Nikos Chantziaras
2009-06-25  2:33                           ` Mark Knecht
2009-06-25  8:47                         ` bn
2009-06-25 17:42                           ` Mark Knecht
2009-06-24  9:21           ` Peter Humphrey
2009-06-24 14:25         ` 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='h1rr9f$hm0$1@ger.gmane.org' \
    --to=realnc@arcor.de \
    --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