[Starkit] filleting tcllib

[Arjen Markus]

Jean-Claude Wippler wrote:
> 
> Arjen Markus wrote:
> 
> > Steve Blinkhorn wrote:
> >
> >> Has anyone given any thought to a method for filleting tcllib, i.e.
> >> specifying a list of packages known to be required, [...]
> >
> > Most of the time I only need one or two packages and figuring out
> > which to include has been relatively simple sofar.
> >
> > Perhaps rather than a programmatic solution, we should provide
> > a chart depicting which packages are required by which others?
> 
> A simple text file which contains all "A depends on B" dependencies
> as a Tcl-readable text file, say as "A B\n" lines could go a long way.
> 
> Could add a third item perhaps, for cases where dependencies are
> platform-specific or depend on the presence of other packages.  Easy
> to ignore for simple-minded uses of this datafile.
> 
> I'd vote for having such a text file included in the tcllib distro,
> then anyone can come up with whatever automation scripts they like.
> Let's make a start with dependency-awareness in the world of Tcl
> packages, without it we'll never reach any sort of repository solution!
> 

Exactly:

Start with a lightweight solution and then turn to complete automation. 

Regards,

Arjen