Max Horn wrote:
[]
As a solution, I currently think of this setup: Add another splitoff
FOO-common to FOO. Move all the common stuff there. Leave FOO itself
mostly empty. Add Depends: FOO-common to the PMs, and add Depends on
the PMs to FOO itself.
But doesn't the latter force you to build
Am 28.03.2006 um 13:28 schrieb Martin Costabel:
Max Horn wrote:
[]
As a solution, I currently think of this setup: Add another
splitoff FOO-common to FOO. Move all the common stuff there. Leave
FOO itself mostly empty. Add Depends: FOO-common to the PMs, and
add Depends on the PMs to FOO
Hi folks,
I was wondering: Is there any sane way to specify a common splitoff
for a package with variants? The background for this questions it the
polymake package on our package submission tracker https://
sourceforge.net/tracker/?
func=detailatid=414256aid=1114201group_id=17203, but I
On Tue, Mar 28, 2006 at 02:22:05AM +0200, Max Horn wrote:
Hi folks,
I was wondering: Is there any sane way to specify a common splitoff
for a package with variants?
There's no way to have a single .info that contains a splitoff that is
less varianted than the parent. If a .info has
