public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Graham Murray <graham@gmurray.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: how to recover a portage that wasn't in use for  very long time
Date: Wed, 13 May 2009 16:30:09 +0100	[thread overview]
Message-ID: <87predja0u.fsf@newton.gmurray.org.uk> (raw)
In-Reply-To: <58965d8a0905130814h5bc9b3e0nbc0f6fbdb1cb9b69@mail.gmail.com> (Paul Hartman's message of "Wed, 13 May 2009 10:14:07 -0500")

Paul Hartman <paul.hartman+gentoo@gmail.com> writes:

> buildsyspkg in FEATURES (make.conf) can be a life saver too :)

But it does not (IMHO) save binaries for enough packages. For example,
it saves a binary for portage but not for python. I think it would be
good if it saved a binary package for everything which would be built
in stage-1, which would provide a much better 'get out of jail free' if
a critical package gets corrupted or fails to run.



  reply	other threads:[~2009-05-13 15:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10  0:58 [gentoo-user] how to recover a portage that wasn't in use for very long time Alexey Luchko
2009-05-10  1:54 ` Mike Kazantsev
2009-05-10  1:56   ` Mike Kazantsev
2009-05-10 12:20 ` Stroller
2009-05-10 17:31 ` Alan McKinnon
2009-05-10 19:25   ` [gentoo-user] " Francesco Talamona
2009-05-10 22:31 ` [gentoo-user] " Nick Fortino
2009-05-12 13:56   ` Alexey Luchko
2009-05-13 10:03 ` [gentoo-user] " Alexey Luchko
2009-05-13 10:17   ` Alan McKinnon
2009-05-13 14:16     ` Stroller
2009-05-13 14:27       ` Alan McKinnon
2009-05-13 14:49         ` Stroller
2009-05-13 15:00           ` Alan McKinnon
2009-05-13 15:14             ` Paul Hartman
2009-05-13 15:30               ` Graham Murray [this message]
2009-05-13 15:44                 ` Paul Hartman
2009-05-13 16:55                 ` Neil Bothwick
2009-05-13 14:33   ` Stroller

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=87predja0u.fsf@newton.gmurray.org.uk \
    --to=graham@gmurray.org.uk \
    --cc=gentoo-user@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