Thanks Gustaf
I'd never come across this before since I always use a debian packaged
tcllib.
It's easy enough to pass DTPLITE=dtplite during the build process so it's a
simple workaround whether the change stays or goes.
Thanks for filling me in.
Regards,
--
David
On 9 January 2014 11:06, Gustaf Neumann <neum...@wu.ac.at> wrote:
>
> The problem are installations with multiple tcl and multiple tcllib
> installations, where e.g. the public installation of tcl does not contain
> tclllib, or an ancient version of tcllib, or installations not having tcl
> or tcllib installed in the public path. The change has a self-contained
> install dir for naviserver in mind, where e.g. /usr/local/ns contains a
> tclsh and a tcllib (using "--prefix=/usr/local/ns", as it is the case with
> the install scripts for naviserver + openacs from openacs.org). ... but
> you are right, one cannot assume this in general ... but "build-doc" is
> just for developers (the tar file releases of naviserver contain the
> generated manual pages)
>
> i am somewhat reluctant to extend "autoconf" for developers to require
> tcllib (in a matching version).
> For now, one can use "make DTPLITE=dtplite build-doc"; maybe it is better
> to keep the old version around for us few developers, and pass the a
> matching "DTPLITE=..." in for the full install script, that knows where tcl
> and tcllib is residing, ... unless someone has a better suggestion.
>
> -g
>
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
