Re: [ECOS] Splitting out Jim to a seperate module from athttpd

[Andrew Lunn <andrew at lunn dot ch>]

On Thu, Nov 15, 2007 at 09:41:42AM +0200, Sergei Gavrikov wrote:
> On Thu, Nov 15, 2007 at 08:10:28AM +0100, ?yvind Harboe wrote:
> > Is there a reason why Tcl Jim is inside the athttpd package?
> > 
> > It may be possible to use Tcl Jim without using the athttpd stuff when
> > adding the athttpd package, and if so, it's only a matter of lack of
> > documentation/marketing of that feature + I guess an estethic thing(no
> > observable difference in executables by a seperate package) to split
> > out seperate features in seperate packages. I haven't checked, but the
> > athttpd probably relies on tcp/ip stuff which would make ecosconfig
> > refuse to add that package in an environment without tcp/ip.
> 
> It seems, that eCos Jim package must live here
> 
> 	$ECOS_REPOSITORY/language/tcl/jim

If i remember correctly, Bart raised the same question when athttpd
was submitted. I suggest looking back in the archive for the
discussion at the time.

           Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss