Hi again,
Comments below, in order:
>>>> Thanks for the feedback everyone.
>>>> There was also some discussion of creating a more minimalist variant
>>>> without all of the extension language bindings.
>>>> So how does the following sound?
>>>> graphviz-base (no x11, no language plug-ins, just dot and friends)
>>>>
>>> graphviz-base sounds like it's the core package that has other sub
>>> packages available that add further features. In fact, that's what a
>>> lot of the kde packages do:
>>> <http://pdb.finkproject.org/pdb/browse.php?name=base> Maybe
>>> graphviz-basic or graphviz-minimal?
>>
>> On the other hand, I believe that's the way tetex is packaged:
>>
>> with tetex conflicting with/replacing tetex-base and tetex-nox
>> conflicting with/replacing tetex-nox-base.
>>
>> I'm not sure that's an actual policy for this or if one is really
>> necessary. For what it's worth, my personal choice is David's original
>> suggestion.
>>
>>>> graphviz-nox (no x11, but with 'all' language plug-ins)
>>>> graphviz (with x11, gtk+pangocairo, all the fixins
>>
>> --
>> monipol
>> http://finkers.wordpress.com
>>
> For what it's worth: 'tetex' is just a placeholder needed to install an
> X11-enabled teTeX distro and Depends: tetex-base, and 'tetex-nox' does
> the same thing for an X11-less version, Depending on tetex-nox-base.
> There used to be a bundle-tetex package, and 'tetex' acually contained
> useful stuff, but that shifted around. They both Depend on the
> respective tetex-base
There will be no dependencies between graphviz variants. graphviz-base
(whatever we name it) will have to conflict/replace other sibling variants
*unless* there is an easy and reliable way to separate out a plug-in-only
build/package (not via split-off b/c that would still bring in all the
optional deps). (Unpack the whole thing and rebuild, but strip out files
already installed by the -base package?)
> Does X11 only play a role in the plugins? If so, then something like
>
> graphviz-base
> graphviz-plugins-nox | graphviz-plugins
>
> would be appropriate in that case, and a "graphviz | graphviz-nox"
> bundle package to depend on both the -base and -plugins.
I *believe* that the language plug-ins are orthogonal to the x11 features.
The plug-ins are for accessing the internals of graphviz through some API.
(I can't say with 100% certainty because I haven't used them.) So
technically, there could exist an x11 version without language bindings,
which would make a two-level variant (4 combinations) more appropriate.
I can see that there is quite a bit of work to do on this.
Should I try to make all such revisions in one shot? or perhaps do this
more incrementally, starting with just the -nox variant, and then work on
plug-ins in the next revision? What makes more sense?
Fang
David Fang
http://www.csl.cornell.edu/~fang/
http://www.achronix.com/
------------------------------------------------------------------------------
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
