Subject: Re: Alternatives in the same package
To: Adam Ciarcinski <firstname.lastname@example.org>
From: Mike M. Volokhov <email@example.com>
Date: 04/20/2005 15:41:39
On Wed, 20 Apr 2005 13:58:54 +0200 (CEST)
Adam Ciarcinski <firstname.lastname@example.org> wrote:
> > 2) Use variable named, say, USE_LANG which may be set to "ruby" or
> > "perl" at the build stage. Resulted package name may be also dependent
> > on the selected value for USE_LANG. The conflicts will be also handled.
> > Any opinion, how to create such packages?
> I would say: if the two implementations work independently, split the
> package in two: -ruby, -perl. If you can choose between the two options,
> or have them both compiled at the same time, then use options.mk
Yes, options framework seems much better rather custom variables.