public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthias Langer <mlangc@gmx.at>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gcc-3.4 migration guide
Date: Sun, 04 Dec 2005 02:46:44 +0100	[thread overview]
Message-ID: <1133660805.9232.12.camel@sputnik886.ruz-net> (raw)
In-Reply-To: <43924891.5050604@gentoo.org>

On Sat, 2005-12-03 at 21:38 -0400, Luis F. Araujo wrote:
> Matthias Langer wrote:
> 
> >On Sat, 2005-12-03 at 14:04 -0700, Joshua Baergen wrote:
> >  
> >
> >>Matthias Langer wrote:
> >>    
> >>
> >>>2.) emerge -e world on a system with lot of packages will most likley
> >>>fail somewhere during the process for various reasons. Fixig the problem
> >>>(for example by unmerging the package which causes it) and restarting
> >>>the process is not an option, as this may cost you lot's of time. In my
> >>>case, emerge -e world stopped 3 times. To continiue without starting it
> >>>all again, i did 
> >>>
> >>># emerge --resume -p > package.list 
> >>>
> >>>and then edited this file with vi so that 
> >>>
> >>># emerge --oneshot --nodeps `cat package.list` 
> >>>
> >>>  
> >>>      
> >>>
> >>You'd probably be interested in 'emerge --resume --skipfirst'.
> >>    
> >>
> >
> >:-) well, this is just the kind of information i had expected to find in
> >the migration guide.
> >
> >By the way, please don't get me wrong, i highly appreciate the hard work
> >you are all doing - gentoo really is a great project and my remarks here
> >in this list have the sole purpose to make it eaven better.
> >  
> >
> I don't know if somebody recently updated it, but this is on the guide.

Well, my fault - maybe i just missed that - sorry.
Matthias

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-12-04  1:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 21:55 [gentoo-dev] GCC-3.4 will be marked stable in ~1 hour on x86 Mark Loeser
2005-12-03  0:36 ` Philip Webb
2005-12-03 12:47 ` [gentoo-dev] emerge -e question Was: " Duncan
2005-12-04  2:13   ` Jason Stubbs
2005-12-04  9:18     ` [gentoo-dev] " Duncan
2005-12-03 14:46 ` [gentoo-dev] " Jan Kundrát
2005-12-03 20:26   ` [gentoo-dev] gcc-3.4 migration guide Matthias Langer
2005-12-03 20:08     ` Marius Mauch
2005-12-03 20:31     ` Jan Kundrát
2005-12-04  1:16       ` Matthias Langer
2005-12-04  1:37         ` Luis F. Araujo
2005-12-04 16:11       ` [gentoo-dev] " Jeff Grossman
2005-12-03 21:04     ` [gentoo-dev] " Joshua Baergen
2005-12-04  1:28       ` Matthias Langer
2005-12-04  1:38         ` Luis F. Araujo
2005-12-04  1:46           ` Matthias Langer [this message]
2005-12-04 23:24 ` [gentoo-dev] GCC-3.4 will be marked stable in ~1 hour on x86 Georgi Georgiev

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=1133660805.9232.12.camel@sputnik886.ruz-net \
    --to=mlangc@gmx.at \
    --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