enabling/disabling features (Was Re: RE Questions with Auke Kok)

[Couannette]

Hey,
we understand eo !
Just : in much cases you would select an optional dependency and lin 
just install the dependency for you.
You don't have a mecanism for systematicaly choose 
--enable-foo/--disable-foo. I mean a way to bypass autodetection of 
software previously installed at configure time. IHM a small matrix for 
each enable/disable would be a greate improvement.
Example : I've installed alsa-* stuff. But I decided to use OSS 
emulation. Now I use OSS kernel driver and I don't want anymore 
applications be linked against alsa-*. I've no way to specify this. (Btw 
I can't uninstall alsa-* because it's required by some apps.)

You follow my thinking ?

Couannette

Jasper Huijsmans wrote:

>Hey,
>
>If I understand you correctly, this is already possible using
>optional_depends. It allows you to add extra arguments to configure
>(like --enable-foo/--disable-foo).
>
>	Jasper
>
>
>On Tue, 01 Jul 2003 19:54:24 +0200
>Couannette <couannette at free.fr> wrote:
>
>  
>
>>Hi Lunar People,
>>
>>I would like to introduce a small debate about one very simple thing.
>>If you want a application to be installed and built with a particular 
>>set of features (libraries) you can't do that if you previously 
>>installed theses features. Autoconf will automatically detects them
>>and configure your app to use them.
>>
>>Perhaps autoconf need a new stage of conception, perhaps standard 
>>features matrix can be implemented. You would choose before install
>>some application your prefered set of features and LIN would configure
>>this application exactly as you intended.
>>
>>What do you think about that ?
>>
>>Couannette
>>
>>_______________________________________________
>>Lunar mailing list
>>Lunar at lunar-linux.org
>>http://lunar-linux.org/mailman/listinfo/lunar
>>    
>>
>
>
>_______________________________________________
>Lunar mailing list
>Lunar at lunar-linux.org
>http://lunar-linux.org/mailman/listinfo/lunar
>
>  
>