I copied the LiveCD stage1 spec file from the examples that came with catalyst2 and used what appear to be the defaults in that file in an attempt to build a LiveCD. Apparently "kudzu-knoppix" isn't available: ------------------------------------------------------------------------------- emerge --usepkg --buildpkg --newuse livecd-tools dhcpcd acpid apmd gentoo-sources kudzu-knoppix hotplug coldplug fxload irssi gpm syslog-ng parted links raidtools dosfstools nfs-utils jfsutils xfsprogs e2fsprogs reiserfsprogs ntfsprogs pwgen rp-pppoe screen mirrorselect penggy iputils hwdata-knoppix hwsetup lvm2 evms vim pptpclient mdadm ethtool wireless-tools prism54-firmware wpa_supplicant livecd-tools Calculating dependencies - emerge: there are no ebuilds to satisfy "kudzu-knoppix". !!! catalyst: Error in attempt to build packages Traceback (most recent call last): File "modules/generic_stage_target.py", line 1028, in build_packages " build_packages "+mypack,"Error in attempt to build packages") File "/usr/lib/catalyst2/modules/catalyst_support.py", line 434, in cmd raise CatalystError,myexc CatalystError: <unprintable instance object> None !!! catalyst: livecdbuild aborting due to error. ------------------------------------------------------------------------------- This is dev-util/catalyst-2.0_pre20051122. I took the package out of the spec file and it's now happily emerging packages. Is that the right thing to do, or do I need to hunt down "kudzu-knoppix"?
Yeah... kudzu-knoppix has been removed from the tree completely. It never should have been listed in the first place, as it was pulled in as a dependency. Now libkudzu is used, and it is pulled in automatically.
I've changed this in the example specs, but if you notice, those examples are based off 2005.0, so they aren't updated to the current state of the tree. They're there to be a guideline, not to help you duplicate anything that we've done... ;]
(In reply to comment #2) > I've changed this in the example specs, but if you notice, those examples are > based off 2005.0, so they aren't updated to the current state of the tree. > They're there to be a guideline, not to help you duplicate anything that we've > done... ;] Ah ... OK ... there used to be a "current" set of default spec files. Does that still exist?
Yes, the ones from 2005.1, but they only work with catalyst 1.x anyway.