Why do we ship tcl again? (was: Re: [PATCH] Core Update 166: Perform spring clean of orphaned files)

["Peter Müller" <peter.mueller@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]

Hello Michael,
hello *,

looking at

>> +	/usr/lib/tcl8/8.4/platform-1.0.14.tm \
>> +	/usr/lib/tcl8/8.4/platform-1.0.15.tm \
>> +	/usr/lib/tcl8/8.5/msgcat-1.6.0.tm \
>> +	/usr/lib/tcl8/8.5/tcltest-2.4.0.tm \
>> +	/usr/lib/tcl8/8.6/http-2.8.9.tm \
>> +	/usr/lib/tcl8/8.6/tdbc/sqlite3-1.0.4.tm \
>> +	/usr/lib/tcl8/8.6/tdbc/sqlite3-1.1.2.tm \
> 
> Why do we even ship tcl? Is anything reliant on this?

in particular and the tcl rootfile in general, I would like to bring your question up again.

This is especially because the current tcl rootfile ships file I definitely expect in the
sqlite territory, not here:

> #usr/lib/sqlite3.36.0
> usr/lib/sqlite3.36.0/libsqlite3.36.0.so
> usr/lib/sqlite3.36.0/pkgIndex.tcl

To my understanding, this makes it hard to understand if the sqlite version carried out
via tcl takes precedence, or if the _actual_ sqlite version is effective.

Unless anybody has an idea why we actually need to ship tcl, I would like to try out what
happens if we don't. :-)

Thanks, and best regards,
Peter Müller