RE: [gentoo-user] Excellent Paludis interview

> -----Original Message-----
> From: Zsitvai János [mailto:zsitvaij@×××××.com]
> Sent: Friday, December 21, 2007 3:47 AM
> To: gentoo-user@l.g.o
> Subject: Re: [gentoo-user] Excellent Paludis interview
>
> Neil Bothwick <neil@××××××××××.uk> writes:
>
> > On Thu, 20 Dec 2007 08:46:12 -0600, Marzan, Richard non Unisys wrote:
> >
> >> Portage can continue to build packages if one fails.
> >>
> >> # emerge -options package/list_of_packages || until emerge
> >> -same_options_as_before package/list_of_packages ; do : ;done
> >
> > Yes it can, but not with this, which will repeatedly try to build the
> > same package until entropy stops it. You need
> >
> > emerge -opts pkglist || untill emerge --resume --skipfirst; do : ; done
> >
> > but this is a kludge as you will be eying to build packages when their
> > dependencies failed. I would hope the paludis option is more
> intelligent.
> >
>
> Indeed it is. :) From the man page:
>
> --continue-on-failure
> Whether to continue after a fetch or install error
>
> if-fetch-only
> If fetching only (default)
>
> never  Never
>
> if-satisfied
> If remaining packages' dependencies are satisfied
>
> if-independent
> If independent of failed and skipped packages
>
> always Always (UNSAFE)
>
> János Zsitvai
> --
> gentoo-user@g.o mailing list

I'm definitely willing to switch and will most likely do so during the holiday week. Paludis seems to be a favorite amongst experienced users. Which begs the question; Why not redirect all efforts to building a stable, full-featured Paludis as soon as possible and purge portage? One option that I would like is for the build to be done completely in ram until it's compiled and ready to be placed on disk. HDD I/O is the slowest part of the system avoiding it as much as possible on systems with plenty of ram is a good idea.

Regards,

Richard 

-- 
gentoo-user@g.o mailing list