expect package dependencies

[Auke Kok]

umm,

since tk already DEPENDS on tcl, it's not a problem to split it up, the
tcl tarball of course is already available, and can be used for the
compilation process only.

This method also has the advantage that you don't need to ask any
questions at all, since apps either depend on tcl or both (thus depending
on tk), and would be preferred since we called for a memorandum on
optional_depends and CONFIGURE questions.


sofar

on 9 Oct 2003, Hendrik Visage wrote:
> On Thu, Oct 09, 2003 at 06:23:38PM +0200, Auke Kok wrote:
> >
> > Hi,
> >
> > either we split tcl and tk into their respective packages, or we can make
> > a standalone tcl module that can't be combined with the tcl-tk module.
> > Since tk pretty much depends on tcl, we can chain the dependencies easily
> > for tcl-tk apps, and avoid optional_depends at all. Should be relatively
> > simple.
>
> ACtually *not* quite :(
>
> Last time I worked with TK from source, TK needed the TCL source (as per
> the ./configure run) to compile itself :(
>
> _______________________________________________
> lunar mailing list
> lunar at lunar-linux.org
> http://dbguin.lunar-linux.org/mailman/listinfo/lunar
>