Hi, On Tue, May 08, 2007 at 10:32:16AM -0500, Michael Wolf wrote:
On Wed, 2007-05-02 at 21:09 +0200, Dr. Peter Poeml wrote:
I implemented the functionality in a slightly different way.
I'm glad you did. The intent wasn't for it to go into svn as I implemented it -- it was quick and dirty by any standard.
I have to admit that I remembered to look here for the patch, so in fact I started from scratch without thinking. And not because I considered your code unusable. ;)
Second is a patched version of ccache. This links /usr/local/bin/{gcc,cc,g++,c++} to /usr/bin/ccache. The result is that ccache is transparently invoked when building, no need modify your .spec or anything like that. Also, the default cache size is raised to 3G and ccache's directory goes into /.ccache. To use, you currently need my patched osc; put the ccache package into your preferred rpms directory and build away.
This calls for an --extra-pacs option. For now, it might be acceptable to put ccache into BuildRequires and let it come from the preferred dir...
I guess, but I'm sure I'll end up forgetting and leaving ccache as a BuildRequire -- not the end of the world, but kind of annoying.
I have implemented a -x / --extra-pkgs option now. It is perfect for adding a preferred ccache package in conjuction with -p. It is also suitable to add debugging tools to the buildsystem. Michael has already added the required support in the backend. If my patch survives some testing, I'll put it in svn later.
Locally, I played with another option today:
-k DIR, --keep-pacs=DIR Save built packages into this directory
This can work hand in hand with --prefer-pacs. Does this sound cool or stupid to anyone?
This sounds like it would be very useful.
That's already implemented since a few days. Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development