On 5/18/06, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
On 5/18/06, Laurent Pelecq <[EMAIL PROTECTED]> wrote:
> Lucas C. Villa Real a écrit :
> > I think the best thing to do is to define "standard"
> > configure_options, and let the user override that later in the command
> > line (with Compile --configure-options) or by modifying the recipe,
> > which might have some commented entries. The latter is already
> > happening in some recipes such as Qt, IIRC.
>
> Maybe it could be possible to have a way to add configure option if a
> package is installed, for example :
>
> configure_options_AAlib=(
>   "--enable-aalib"
> }
>
> This way you can add all the dependencies you want, they would only be
> configured if they are installed.

hmmm, I like this.

There have been several proposals for optional dependencies so far.
Lots of things to think about, like flags, changes in pre_/post_
hooks, etc. What you propose is a step in the right direction (IIRC,
something very similar has already been proposed) but there are many
details surrounding the whole issue, ranging from conceptual topics
down to the implementation (ie, are you going to scan every valid
Compile flag for a <flag>_<depname> variable, etc.).

> The problem if the dependencies are reduced to a minimum is that a user
> may not be aware that there are optional dependencies available. Typically
> for VLC, I guess that most users would like it to support as many format
> as possible while few users would like to restrict the supported format to
> a specific list. With optional dependencies, the dialog would be:
>
> Mandatory dependency libpng is not installed: [i]install/[s]kip ?
> Optional dependency AAlib is not installed: [i]install/[s]kip ?
>
> And when optional dependencies are selected, the recipe takes care of
> enabling it if necessary.

Yes, once we have a scheme for optional dependencies, that's how it
would be used.

Right. So, can we use the current Dependencies script to generate the
optional dependency list? Seems sane to me.

No. Quite frankly, the current Dependencies is not reliable (when
talking about automating upgrades). All it can be used for is as a
first step when generating a PackageBuildInformation file.

-- Hisham
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel

Reply via email to