>Are you using 'livecd/use: -* ...' in your spec? if so, this will cause portage to completely ignore package.use. This is "normal" behavior and has nothing to do with catalyst.
Yes, I use 'livecd/use: -* ...' in livecd-stage1. I forgot to mention: I also have put my new USE flags in livecd/use, but it still caught the old flags, apparently. I didn't rm the whole livecd-stage1 though. I just re-run catalyst over it. I also tried removing the package from livecd-stage1 from portage db of installed packages: rm -fr /var/tmp/catalyst/tmp/mycd/livecd-stage2.../var/db/pkg/mygroup/mypkg/ That should have forced a recompile of mypkg, but I suspect that catalyst might still find the previous compilation and thus just do a 'make install'. Do you think I should recompile the whole livecd-stage1? Is there a way to selectively remove specific package objects/compilation? I couldn't find where they are stored. >In a package.use files in the portage_confdir specified in your .spec files. Yes. My spec file contains this: portage_confdir: /usr/src/mycd/portage.config In portage.config I have package.use >Did you also delete Catalyst's autoresume points? The '-a' switch does this. Yes, I did, but I run rm -fr /var/tmp/catalyst/tmp/mycd/.autoresume...(livecd2)/ Thank you for your input. I'm starting to see some new possibilities. I will keep you informed about the solution that will work. -- [email protected] mailing list
