> I had wanted to purge everything catalyst has produced so far, however > when I ran catalyst --purge, I get the following error: > !!! catalyst: please specify one of either -f or -C > When I specify both --purge and -f (some spec file) it attempts to build > the stage instead of purge. Should I open a bug for this? > >No, that's how it's supposed to work. The purge isn't an operation all by >itself. It's just an additional step that's performed before a build.
I see! I have done all of this over again using the -p flag and it has built successfully this time... I guess something stuck around in the cache causing these blocks to remain... catalyst -p -f rwmc-stage1.spec && catalyst -p -f rwmc-stage2.spec && catalyst -p -f rwmc-stage3.spec > Here's what I did: > emerge --sync > catalyst -s rwmc.001 > catalyst -f rwmc-stage1.spec > catalyst -f rwmc-stage2.spec > catalyst -f rwmc-stage3.spec > > rwmc-stage1.spec contains: > subarch: x86 > target: stage1 > version_stamp: rwmc.001 > rel_type: default > profile: default/linux/x86/2008.0 > snapshot: rwmc.001 > source_subpath: default/stage3-i686-2008.0 > chost: i686-pc-linux-gnu > > rwmc-stage2.spec contains: > subarch: i686 > target: stage2 > version_stamp: rwmc.001 > rel_type: default > profile: default/linux/x86/2008.0 > snapshot: rwmc.001 > source_subpath: default/stage1-x86-rwmc.001 > chost: i686-pc-linux-gnu > > rwmc-stage3.spec contains: > subarch: i686 > target: stage3 > version_stamp: rwmc.001 > rel_type: default > profile: default/linux/x86/2008.0 > snapshot: rwmc.001 > source_subpath: default/stage2-i686-rwmc.001 > >At first glance, everything here looks fine. I'm not sure what to tell you.
