Personally, I have a "tools" project where I put all this sort of stuff, with corresponding prjconf entry to add build-compare as a support rpm. I then just add the tools repo as a Build Repository to all relevant projects. This is easier than adding build-compare pkg individually to all pkgs. -- Michael ________________________________________ From: jnelson@jamponi.net [jnelson@jamponi.net] On Behalf Of Jon Nelson [jnelson-suse@jamponi.net] Sent: Monday, March 29, 2010 12:34 PM Cc: opensuse-buildservice@opensuse.org Subject: Re: [opensuse-buildservice] build-compare On Mon, Mar 29, 2010 at 12:23 PM, wrote:

You have to have the package available so that it can be pulled into the chroot environment, and add it as a "Support" package in your prjconf.

The build compare stuff will show up in your build logs at the end, if it is being used.

Does it have to be added to all projects (like home:* projects), their "upstream" projects, etc... -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Mon, Mar 29, 2010 at 01:22:26PM -0500, Jon Nelson wrote:

On Mon, Mar 29, 2010 at 1:11 PM, wrote:

...

Personally, I have a "tools" project where I put all this sort of stuff, with corresponding prjconf entry to add build-compare as a support rpm. I then just add the tools repo as a Build Repository to all relevant projects. This is easier than adding build-compare pkg individually to all pkgs.

AAh. Wait. So installing the build-compare package on the actual OBS server doesn't help. The package has to be installed in the actual build environment when the package is built. One way to do this is with the project conf stuff, but the package itself still has to be available.

Yes, that is exactly correct. -- Michael