From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-user+bounces-45819-garchives=archives.gentoo.org@gentoo.org>)
id 1Fyy2Z-00005C-1I
for garchives@archives.gentoo.org; Fri, 07 Jul 2006 21:39:11 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k67LbBYa010023;
Fri, 7 Jul 2006 21:37:11 GMT
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174])
by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k67LV8VZ013087
for <gentoo-user@lists.gentoo.org>; Fri, 7 Jul 2006 21:31:09 GMT
Received: by ug-out-1314.google.com with SMTP id j40so857530ugd
for <gentoo-user@lists.gentoo.org>; Fri, 07 Jul 2006 14:31:09 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
b=nuuV3OnfnAQItUNKzj7xeKYP4am/sp7oiJ/SAAm05smw5O7DeR/f+WMpp7jTS6SbduT/7v9wt4eUGSsubVMDBFXCO44wDN6GoAxL7GQTfkzXPq17zTCWSuBvTFwnDt7In2toe4/hYToKmMUqbpW6P5kDr5OQZS99GS/5XB/qX0I=
Received: by 10.66.243.2 with SMTP id q2mr2470325ugh;
Fri, 07 Jul 2006 14:31:08 -0700 (PDT)
Received: by 10.66.243.7 with HTTP; Fri, 7 Jul 2006 14:31:08 -0700 (PDT)
Message-ID: <342e1090607071431lbf89492j30a0fc7693381d42@mail.gmail.com>
Date: Fri, 7 Jul 2006 18:31:08 -0300
From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Things that can be improved
In-Reply-To: <7573e9640607071412u6ef9750btfceae4bacf5f9dde@mail.gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Disposition: inline
References: <44AEB475.8000702@maestroprogramador.com>
<7573e9640607071412u6ef9750btfceae4bacf5f9dde@mail.gmail.com>
X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id k67LV8VZ013087
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id k67LbBYr010023
X-Archives-Salt: 97dc26fe-a9ab-43a6-b7b9-f249d3262930
X-Archives-Hash: 433eefa5c2ee7714c91fab1a48e4a14d
On 7/7/06, Richard Fish <bigfish@asmallpond.org> wrote:
> On 7/7/06, Rafael Fern=E1ndez L=F3pez <info@maestroprogramador.com> wro=
te:
> > The first thing that I'd change is "etc-update" or "dispatch-=
conf". I'd
> > suggest to create some kind of tool like "dpkg-reconfigure" in Debian.
>
> I don't know anything about dpkg-reconfigure, so I can't really comment=
on this.
>
> But one thing I really do like about gentoo is that I *can* go modify
> configuration files directly, without worrying about some distribution
> tool clobbering my changes, or choking on something it wasn't setup to
> deal with. This is one of the things that drove me from SuSE. I
> would really object to some kind of "configuration file configurator"
> app.
>
> > Second thing that I'd improve is a security one. I know that =
"emerge"
> > is a very cared package, but it is a script. Suppose that someone
>
> I think this is a non-issue. Something like this would be found
> incredibly quickly by the portage devs working in their overlay, and
> they would know how to fix it. In the worst of all possible cases, it
> might theoretically make it to the ~arch users, who again, presumably
> have enough experience to know how to resurrect their systems without
> resorting to a live CD and re-install.
>
> It is far more likely that you could break python (and thus portage)
> from a mishandled gcc or glibc update. But there is already a
> recovery option available in this case; if you have buildpkg in your
> FEATURES, you will already have a backup copy of
> portage/python/gcc/glibc/everything else in $PKGDIR. Even if portage
> is broken, you can extract those tarballs to get back to a working
> configuration. Of course, this assumes that tar and bzip2
> work...otherwise you are down to booting from a live CD.
>
>
> One area I do think could be improved is in the update process.
> Currently we have etc-update, revdep-rebuild, fix_libtool_files.sh,
> eselect {opengl,gcc,binutils}, python-updater, perl-cleaner, and so
> on. Each update requires running one or more of these. But which
> ones, when, why, and in what order? I *think* _I_ know the answers to
> those questions, but I would bet most users do not. So I think a
> little more automation (or at least hand-holding) in portage to deal
> with the above would be very useful. Something like:
>
> emerge -DNuv world
> <several hours later>
> Updates done.
>
> Hmm, looks like a new version of python was installed. You should run
> python-updater to make sure all python modules are rebuilt. Do you
> want to do that now?
>
That's more likely to be needed. +1
--=20
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
--=20
gentoo-user@gentoo.org mailing list