On 12/23/2009 05:39 PM, Andreas Jaeger wrote:
On Wednesday 23 December 2009 16:34:49 Dave Plater wrote:
No I think what I want is not possible, I want the three spec files to build in the same package. With the link the linked package gets updated when the main package changes but the rpms are built in the package with the same name as the spec file. It would be a nice feature if build service supported this.
Why do you need it? All packages will end in the same repository since you use the same project. Isn't that enough?
Andreas
ATM bacula can only be built for a specific database, the version in contrib is the mysql version, people are asking for postgresql, which my co-maintainer uses, and the sqlite version. The binaries produced by each build have the same names so this equals either two new packages besides the existing one or the use of update alternatives in the %pre sections of the spec file like vim. When bacula is released early next year with a configurable data base backend only one package and spec file will be needed. If multiple spec files worked in one package this wouldn't be a problem at all. Three seperate packages = three times as many hermes messages, three times as many working copies. Ok I concede that linking the other two to one helps decrease the amount of maintainance but the only difference between the three spec files are the package name and the line --with-mysql substituted with --with-postgresql substituted with --with-sqlite. I'm not complaining, I'll just carry on and get the job done in the best way I can. All I said was, it would be a nice feature if multiple spec builds were possible. I'm an unpaid community member who maintains three packages besides bacula and multiple spec builds in one package would make my life easier and maybe a few other people's. Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org