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 ) id 1FyxvK-0007mT-1j for garchives@archives.gentoo.org; Fri, 07 Jul 2006 21:31:42 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k67LRnnd018194; Fri, 7 Jul 2006 21:27:49 GMT Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k67LCDnN015147 for ; Fri, 7 Jul 2006 21:12:13 GMT Received: by ug-out-1314.google.com with SMTP id e2so147464ugf for ; Fri, 07 Jul 2006 14:12:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=H9zfmxzQF8JRXYGWmJ12yAVvDScg5jesLAzfXaUyXB7KF6aJZtHpnp6pu0F+6zt9Va+gGQ7GvD4I77N6/jkmHm+b8RFqBydBQSx0zdQWVP3iJ9viIVHzJnJdJBtmM2+1J7gsaHEEKPLY5LF4o/7SAPuaJusifxWcro3IuW2C6b8= Received: by 10.78.136.7 with SMTP id j7mr883173hud; Fri, 07 Jul 2006 14:12:13 -0700 (PDT) Received: by 10.78.20.11 with HTTP; Fri, 7 Jul 2006 14:12:13 -0700 (PDT) Message-ID: <7573e9640607071412u6ef9750btfceae4bacf5f9dde@mail.gmail.com> Date: Fri, 7 Jul 2006 14:12:13 -0700 From: "Richard Fish" Sender: richard.j.fish@gmail.com To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Things that can be improved In-Reply-To: <44AEB475.8000702@maestroprogramador.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail 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> X-Google-Sender-Auth: 31e11d6af9868622 X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id k67LCDnN015147 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id k67LRnnu018194 X-Archives-Salt: 4b170aa5-b466-4199-ac0e-d0b7796d180e X-Archives-Hash: 8c24c648ffb5c6bf075e5919f7ba60ce On 7/7/06, Rafael Fern=E1ndez L=F3pez wrote= : > The first thing that I'd change is "etc-update" or "dispatch-co= nf". 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 o= n 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 "e= merge" > 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 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? -Richard --=20 gentoo-user@gentoo.org mailing list