From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Why do we ship tcl again? (was: Re: [PATCH] Core Update 166: Perform spring clean of orphaned files) Date: Sun, 03 Apr 2022 14:49:13 +0000 Message-ID: <116e1f18-eb68-b828-d016-c777da2966d1@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2617729575486935905==" List-Id: --===============2617729575486935905== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 \ >=20 > 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 que= stion up again. This is especially because the current tcl rootfile ships file I definitely e= xpect 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 c= arried 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=C3=BCller --===============2617729575486935905==--