You want to also look into if you can eliminate building some of the other subpackages to save build resources. You could even %if %endif wrap all the subpackages you don't want so they don't generate a subpackage at all. I did this with obs-server so that on the architectures that only deploy workers, I only get the obs-worker subpackage out. It eliminated the need for a lot of BuildRequires and made the build faster for those targets. It also saves space in the repository server since there isn't an unused rpms and debs taking up space. Of course, depending on what klipper depends on in the rest of the package, your mileage may vary. On Wed, 2010-01-20 at 08:04 -0600, Michael Schroeder wrote:

On Wed, Jan 20, 2010 at 01:38:48PM +0100, Guido Berhoerster wrote:

...

is it possible to publish only certain subpackages built from a common source package, e.g. is it possible to build kdebase4-workspace and only publish the klipper (sub)package built from it?

There's no easy way.

But I think you can (mis-)use an aggregate to do this. I.e. disable publishing of your package and create an aggregate that only fetches the packages you want to publish. (Also disable "useforbuild" for the aggregate.)

Cheers, Michael.

-- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org