>
> I've managed to create working packages for the ns-2 network simulator and
> it's two dependent packages "otcl" an extension to Tcl, and "tclcl" an
> interface between otcl and C++. They work OK and pass almost all lintian
> checks (a couple of missing man pages and some cleanups to do). I
>
> I've managed to create working packages for the ns-2 network simulator and
> it's two dependent packages "otcl" an extension to Tcl, and "tclcl" an
> interface between otcl and C++. They work OK and pass almost all lintian
> checks (a couple of missing man pages and some cleanups to do). I
On Sun, Jul 29, 2001 at 06:23:03PM +0100, Will Newton wrote:
> 3. The ns package has a quite ludicrous number of different licenses attached
> to it, is there someone who I can get to have a look at it and decide what
> exactly the free-ness of it is? tclcl is also under the old BSD license which
On Sun, Jul 29, 2001 at 06:23:03PM +0100, Will Newton wrote:
> 3. The ns package has a quite ludicrous number of different licenses attached
> to it, is there someone who I can get to have a look at it and decide what
> exactly the free-ness of it is? tclcl is also under the old BSD license whic
I've managed to create working packages for the ns-2 network simulator and
it's two dependent packages "otcl" an extension to Tcl, and "tclcl" an
interface between otcl and C++. They work OK and pass almost all lintian
checks (a couple of missing man pages and some cleanups to do). I know have
I've managed to create working packages for the ns-2 network simulator and
it's two dependent packages "otcl" an extension to Tcl, and "tclcl" an
interface between otcl and C++. They work OK and pass almost all lintian
checks (a couple of missing man pages and some cleanups to do). I know have
6 matches
Mail list logo