[prev in list] [next in list] [prev in thread] [next in thread]
List: gentoo-catalyst
Subject: [gentoo-catalyst] stage4 emerge system always rebuilds baselayout and gcc
From: Peter Stuge <peter () stuge ! se>
Date: 2009-06-04 23:47:37
Message-ID: 20090604234737.24950.qmail () stuge ! se
[Download RAW message or body]
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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic