public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fuper <futurist@directvinternet.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] LibPNG Problems -- good example of Gentoo inherent stability
Date: 18 Apr 2002 21:56:43 -0500	[thread overview]
Message-ID: <1019185004.2935.33.camel@silver.perimeter> (raw)
In-Reply-To: <1019092373.32100.1.camel@inventor.gentoo.org>

On Wed, 2002-04-17 at 20:12, Daniel Robbins wrote:
> I'd recommend that people who don't want to have the latest and greatest
> versions of everything (and everything that goes with it), don't use
> --update with emerge.  That should help you avoid most problems.  We are
> still devising a good distributed QA system, but that hasn't been added
> to Portage yet :)

IMHO very little change is needed in Portage --- the libpng conflict was
not a show stopper as it might be in a binary-based Linux distrib. 
Thinking about my experience with the somewhat time-consuming but
relatively straight-forward re-compilation from sources that was
required to update my Gentoo system after encountering a conflict over a
basic library, and my experiences with horrible messes on Redhat and
Debian systems that simply left some applications (KDE!) unuseable for a
while (waiting for developers to create on their computers new sets of
binaries that ANY user can create for himself on a Gentoo system) I've
concluded that a source-based distribution like Gentoo is inherently
stable.  Sure, we stress it, but THAT is the goal --- to make a
distribution that acknowledges and takes advantage of the wonderful
chaos of Linux's multiple, independently developed streams of software.

Actually I'd be a heck of a lot more interested in SHRINKING and
SIMPLIFYING Portage and merging it with a boot loader such that the boot
loader could recover a functional operating system onto an empty hard
drive entirely off the net, entirely from sources.  Then shrink the boot
loader onto a BIOS chip, and then convert unsaved computers to Linux by
popping a new EEPROM onto each motherboard, .....






  reply	other threads:[~2002-04-19  2:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18  0:54 [gentoo-dev] LibPNG Problems :( Eugenia Loli-Queru
2002-04-18  1:12 ` Daniel Robbins
2002-04-19  2:56   ` Fuper [this message]
2002-04-18  5:50 ` Spider

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=1019185004.2935.33.camel@silver.perimeter \
    --to=futurist@directvinternet.com \
    --cc=gentoo-dev@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