On Wednesday 23 December 2009 19:22:56 Dave Plater wrote:
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.
Why working copies three times? Just use the master of the links and have a script that generates - like it's done for gcc and libqt4 (pre_checkin.sh) from one version the other spec files and the changes file. Then you work on the one version and just update that one, run pre_checkin.sh at the end - and the others get rebuild automatically.
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.
You're not the first to hit this problem and we have invented some solutions for these already as described. Please help us documenting this better - and then let's see what can be done to make it easier using, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126