Hey all – I updated my private fork of Catalyst to support “unstable” (aka “tilde”, ie ~x86, ~amd64) builds of Gentoo. Everything from the catalyst side seems to be working, but no unstable stages are available yet as I’m hitting some bugs in the core toolchain.
We (me and Gentoo devs on bugs.gentoo.org) are working to try to resolve these bugs. The current one relates to coreutils-6.12’s /bin/touch using a potentially unsupported system call.
Once all the issues are resolved, I should have some nice “unstable” stages for all of you. :)
For my version of catalyst, I am using the following naming convention for unstable stages:
~[subarch]/funtoo-~[subarch]-[yyyy].[mm].[dd]/stage[x]-~[subarch]-[yyyy].[mm].[dd].tar.bz2
So an unstable core64 build done today would look like this on the filesystem:
~core64/funtoo-~core64-2008.08.01/stage3-~core64-2008.08.01.tar.bz2
I always like to adopt intuitive and useful conventions for naming and organizing data, and simply adding a tilde to the pathing structure was the easiest way to do this.
In the catalyst code itself, catalyst now recognizes a tilde subarch such as ~pentium4, etc, and will automatically insert an ACCEPT_KEYWORDS=”~x86” or “~amd64” into /etc/make.conf when buliding an unstable stage. I actually also insert an ACCEPT_KEYWORDS=”x86” or “amd64” into /etc/make.conf for stable builds, just to be explicit about what tree they are being built against.
I’m hoping that you’ll be able to enjoy the goodies soon.
You have already tagged this post. Your tags: