On November 30, 2014 6:49:56 AM EST, Martin Koegler
Greg Freemyer
wrote: I did some rpm-related reading about subpackages and not being sure whether I understood properly visited #rpm.org when I was told that one cannot have %build section per subpackage. Moreover, I was suggested to create a new package and use 'Conflicts' in each one.
Remember, bogofilter and bogofilter-sqlite are actually *two different* and conflicting packages despite using the same source since both produce single executable, one uses (Berkeley) DB back-end and the other one uses Sqlite3.
So, considering the above do you still consider that subpackage is
On Sun, Nov 30, 2014 at 09:49:47AM +0100, Gour wrote: the
appropriate solution and if yes, can you give some hint how to have different invocation of ./configure for main and subpackage?
Look at the php5 package.
Subpackages will not work, if two (sub-)packages need to ship different content for one path. In that case, you could put two spec files in one OBS packages (see binutils/gcc).
Regards, Martin
The kernel packages are another example of a single master package with multiple spec files. The trick with that approach as it relates to bogofilter/bogofilter-sqlite is you have to have a separate package for each, but the packages should be linked, not standalone. These are the kernel instructions I just copied from evergreen wiki page: == login=JohnDoe osc copypac Kernel:SLE11-SP1 kernel-source home:$login:Evergreen-11.1 for p in kernel-{default,desktop,pae,xen,vanilla,syms}; do osc linkpac -C copy home:$login:Evergreen-11.1 kernel-source home:$login:Evergreen-11.1 $p done == In this case bogofilter and bogofilter-sqlite would be linked packages. You would have 2 spec files: bogofilter.spec and bogofilter-sqlite.spec The bogofilter package will automatically ignore the bogofilter-sqlite.spec file and vice versa. (just be sure to name the spec files after the project names; obs knows what to do from that point.) The packages share the tarball, patches, and changes file so no extra maintenance is needed to maintain both. And it becomes obvious to people modifying one of the spec files they need to modify both. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org