public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Henrik Brix Andersen <brix@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] i have an idea ! (erescue)
Date: Sun, 15 May 2005 23:21:51 +0200	[thread overview]
Message-ID: <1116192111.13692.1.camel@sponge.fungus> (raw)
In-Reply-To: <200505151718.06501.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 904 bytes --]

On Sun, 2005-05-15 at 17:18 -0400, Mike Frysinger wrote:
> 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

Having been in a similar situation a couple of times myself, I think
that's a fantastic idea.

./Brix
-- 
Henrik Brix Andersen <brix@gentoo.org>
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-15 21:18 [gentoo-dev] i have an idea ! (erescue) Mike Frysinger
2005-05-15 21:19 ` Tom Wesley
2005-05-15 21:21 ` Henrik Brix Andersen [this message]
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=1116192111.13692.1.camel@sponge.fungus \
    --to=brix@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