From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#27217: texlive is too big Date: Thu, 10 Jan 2019 16:34:25 +0100 Message-ID: <87muo84jcu.fsf@elephly.net> References: <87tw3w7v1m.fsf@elephly.net> <87po1g2g43.fsf@gmail.com> <87fu2chu02.fsf@elephly.net> <87lgc42b7i.fsf@gmail.com> <87va2wdfq8.fsf@gnu.org> <87pnt44zc7.fsf@ambrevar.xyz> <87wonc4rvg.fsf@elephly.net> <87o98o4qwn.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:60480) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ghcci-0006DP-Ij for bug-guix@gnu.org; Thu, 10 Jan 2019 10:52:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ghcNG-000126-Nq for bug-guix@gnu.org; Thu, 10 Jan 2019 10:36:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:54813) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ghcNG-00011u-Ej for bug-guix@gnu.org; Thu, 10 Jan 2019 10:36:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ghcNG-0006LD-1d for bug-guix@gnu.org; Thu, 10 Jan 2019 10:36:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87o98o4qwn.fsf@ambrevar.xyz> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Pierre Neidhardt Cc: 27217@debbugs.gnu.org Hey Pierre, > I'm so sorry for the poor wording, Ricardo, it was uncalled for. (Wrote = in a > haste.) What I meant is that it does not solve the current issue of "wha= t file > belongs to what package." No worries :) > It's not just the importer but our current approach to TeXlive that we've= got to > work out. I agree. It=E2=80=99s always been messy and currently it=E2=80=99s pretty = frustrating to package or update TeXlive packages. What I find most troubling is that sources are littered across the SVN repository. Sometimes we=E2=80=99ve got simple .ins and .dtx files, but ve= ry often we have a stray .sty or .tex file in some seemingly arbitary directory and one needs to manually take care of adding these extra source files to the native-inputs. This could be improved even before a full overhaul of our TeXlive handling: add a convenience procedure that takes a list of file names in the repository and collects them via SVN as the source tree. Beats having to add extra build phases and the like. >> : I'm more and more convinced that rewriting the texlive-build-system ce= ntered >> : around texlive.tlpdb would work and is the right approach. >> >> Could you please outline what this would mean? > > Sure: if you look at the file, you'll see it's a textual database of all > packages with their respective file. A possible solution that we could > implement either as a build-system or an importer: lookup the package in = the tlpdb > (e.g. mflogo) and package all the corresponding file from the svn repo. = Sounds > simple enough. What do you think? I don=E2=80=99t see this file in the texlive SVN repository. Where is it hosted? So, it=E2=80=99s a map of packages to file names? That would probably simp= lify the importer. I don=E2=80=99t think it would help with the build system. = Am I missing something? -- Ricardo