andrewski wrote:MG-Cloud wrote:Hey,
I've been using fluidportage for a few cvs things and was just wondering ... is it possible to make it not clean the working files so that only stuff that has changed gets rebuilt? That would do wonders for time spent compiling =)
Did you see my original post where I said you can use
to do exactly that?
Perhaps I wasn't really clear ...
For example, when compiling the kernel, once it's compiled, and you add a patch or change a config option or something, and then 'make' again, it only compiles files that have been changed.
The fluidmanager --pkgs-upgrade command re-emerges the packages with changes in cvs, creating a new workdir for each (at least on my system with my *one* cvs ebuild testcase).
From my limited understanding of the build process (newb!

) it seems that if a 'make clean' is not performed on the source directory, much of the compiled code remains there and can be used in subsequent compiles to avoid recompiling the exact same code. I could be horribly wrong here, but that's the way it's seemed to work when I've been compiling stuff manually
Anyways, hope that clarifies things, and if the fluidmanager --pkgs-upgrade thing can actually do what I'm describing, then there must be something I'm doing wrong

Any idea what that would be?
And thanks for the guide ! Up until now I've only been able to do small things with cvs packages.