public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] i have an idea ! (erescue)
Date: Sun, 15 May 2005 17:18:06 -0400	[thread overview]
Message-ID: <200505151718.06501.vapier@gentoo.org> (raw)

one advantage that other binary based package managers have over Gentoo is 
ease of recovery from broken core packages ... break your gcc ?  no problem !  
simply do `apt-get install gcc` or `rpm -i gcc` or whatever

my proposal is to implement a new utility (called 'erescue' for lack of a 
better name) that is written in C and designed to be statically linked ... 
then next time you break a core system package which cannot be recovered by 
simply running `emerge` a few times, you run `erescue <broken package>`

for example, when i broke binutils in unstable with a gcc4 patch, i noticed 
that it's hard for users to *easily* recover from this ... we developers end 
up scrambling to build a bunch of binary packages for a variety of compatible 
compiler/libc combinations so the user can just wget the file and run `emerge 
binutils.tbz2` and be on their way

the packages that would be eligible for an 'erescue' package would be just 
about everything when you do `USE=-* emerge system -ep` ... i'm sure we can 
trim many of those out though :)  maybe even create a new USE flag for some 
of these core packages so that we can trim out more files

the idea would be to create very bare min packages so that the user can simply 
'rescue' themselves ... after that, they it's up to them to re-emerge the 
package to apply all their fun ricer-optimizations as they see fit

i dont think it'd be too hard to integrate this 'rescue set' into a catalyst 
target so that it'll become part of our normal release schedule of stage 
tarballs
-mike
-- 
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2005-05-15 21:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-15 21:18 Mike Frysinger [this message]
2005-05-15 21:19 ` [gentoo-dev] i have an idea ! (erescue) Tom Wesley
2005-05-15 21:21 ` Henrik Brix Andersen
2005-05-15 21:24 ` Carlos Silva
2005-05-16 13:44   ` Chris Gianelloni
2005-05-15 21:29 ` Krzysiek Pawlik
2005-05-15 22:32   ` Donnie Berkholz
2005-05-15 22:45     ` Krzysiek Pawlik
2005-05-15 22:48     ` Ryan
2005-05-15 23:29       ` Sami Samhuri
2005-05-15 23:41     ` david stanek
2005-05-16  0:22       ` Mike Frysinger
2005-05-16  1:12       ` John Myers
2005-05-16  1:56         ` David Stanek
2005-05-16  2:24           ` David Stanek
2005-05-16 10:24           ` [gentoo-dev] " Duncan
2005-05-16 11:20             ` Jan Kundrát
2005-05-16 13:38               ` [gentoo-dev] " Duncan
2005-05-16 13:48                 ` Jan Kundrát
2005-05-16 11:33             ` [gentoo-dev] " Thomas de Grenier de Latour
2005-05-16 13:48               ` [gentoo-dev] " Duncan
2005-05-15 21:31 ` [gentoo-dev] " Olivier Crête
2005-05-16 13:57   ` Chris Gianelloni
2005-05-16 22:11     ` Pete Ezzo
2005-05-17  0:48     ` Olivier Crête
2005-05-17 16:51       ` Chris Gianelloni
2005-05-17 17:33         ` Donnie Berkholz
2005-05-17 17:51           ` Chris Gianelloni
2005-05-24 21:11             ` [gentoo-dev] i have an idea ! (erescue) ro-overlays Jim Northrup
2005-05-24 21:48               ` Mike Frysinger
2005-05-24 22:34                 ` Jim Northrup
2005-05-24 22:40                   ` Mike Frysinger
2005-05-24 23:44                     ` Stuart Longland
2005-05-25 13:32               ` Chris Gianelloni
2005-05-25 16:50                 ` James Northrup
2005-05-16  4:07 ` [gentoo-dev] i have an idea ! (erescue) Sami Samhuri
2005-05-16  4:29   ` David Stanek
2005-05-16  7:09     ` Colin Kingsley
2005-05-16  8:48 ` Chris Bainbridge
2005-05-18  7:07 ` [gentoo-dev] " R Hill

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=200505151718.06501.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@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