public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-catalyst] stage4 emerge system always rebuilds baselayout and gcc
@ 2009-06-04 23:47 Peter Stuge
  0 siblings, 0 replies; only message in thread
From: Peter Stuge @ 2009-06-04 23:47 UTC (permalink / raw
  To: gentoo-catalyst

I run catalyst -c myconf -f stage4.spec and let it run until all
packgaes are built. I stop catalyst with Ctrl-C, remove the resume
point file build_packages from the .autoresume-directory.

I rerun catalyst-c myconf -f stage4.spec, and it is working here at
the moment:

emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps
virtual/portage
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.1.6.11
>>> Installing sys-apps/portage-2.1.6.11
 * GNU info directory index is up-to-date.
Bringing system up to date using profile specific use flags
emerge --quiet --usepkg --buildpkg --newuse -u system
>>> Verifying ebuild manifests
>>> Starting parallel fetch
>>> Emerging (1 of 2) sys-apps/baselayout-1.12.11.1
>>> Installing sys-apps/baselayout-1.12.11.1
>>> Emerging (2 of 2) sys-devel/gcc-4.3.2-r3

How come?

Can I avoid this? It takes a while.


//Peter



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-06-04 23:47 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-04 23:47 [gentoo-catalyst] stage4 emerge system always rebuilds baselayout and gcc Peter Stuge

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox