Otherwise we write the last_success_file when the first build succeeds
and prevent the second from executing. Both of these sets of builds
should probably be executed from the same catalyst-auto file...
stage2 runs bootstrap.sh, which made sense when gcc had a
build/bootstrap USE flags that were set in stage1 and 2. But gcc is
fully built in stage1 now, making stage2 a waste of time.
Avoids the following failure:
The following USE changes are necessary to proceed:
(see "package.use" in the portage(5) man page for more details)
# required by dev-python/cryptography-2.2.2-r1::gentoo[-libressl]
# required by dev-python/urllib3-1.22::gentoo
# required by dev-python/requests-2.18.4-r1::gentoo
# required by dev-python/ssl-fetch-0.4::gentoo
# required by app-portage/mirrorselect-2.2.3::gentoo
# required by app-portage/mirrorselect (argument)
>=dev-libs/openssl-1.0.2o-r3 -bindist
On a few x86 livecd specs we are feeding i486 or i686 seed stage but
using "subarch: x86". This subarch results in i386 CHOST in make.conf
which causes some various problems. Adjusting subarch to match the seed
will ensure there is no "CHOST change" situation.
As of catalyst-3.0.2, with USE=system-bootloader we can omit cdtar from
livecd-stage2 specs and catalyst will generate the required bootloader
files. This gives us an updated isolinux & memtest86+, and also adds
UEFI grub for amd64.
Several changes here:
-Fix sorting on previous addition, and elsewhere
-Move several firmwares from net-wireless/ to sys-firmware/
-Remove obsolete prism54-firmware
-Remove iwl* firmware (bundled in linux-firmware)
-Add linux-firmware where it's missing
Some of our livecd specs already have these firmwares but they're
missing on our minimal installcds. Adding these, since this is still
fairly common (albeit old) hw.
By adding savedconfig on linux-firwmare, we can save a few dozen
megabytes by trimming firmwares that are not generally useful on
livecds. This flag activates the savedconfig file which was recently
added to portage/isos/savedconfig/.
