From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#27217: texlive is too big Date: Tue, 19 Mar 2019 22:36:21 +0100 Message-ID: <87wokulf6y.fsf@elephly.net> References: <87tw3w7v1m.fsf@elephly.net> <87po1g2g43.fsf@gmail.com> <87fu2chu02.fsf@elephly.net> <87lgc42b7i.fsf@gmail.com> <87va2wdfq8.fsf@gnu.org> <87zhs84urk.fsf@elephly.net> <87h8egd7zd.fsf@gnu.org> <878szooiix.fsf@elephly.net> <87a7jzy6ae.fsf@gnu.org> <87sgxr62p1.fsf@ambrevar.xyz> <87munzh8kj.fsf@elephly.net> <87imynsgxg.fsf@ambrevar.xyz> <87k1j3h7k4.fsf@elephly.net> <87imx1e541.fsf@ambrevar.xyz> <86bm2skozm.fsf@fsfe.org> <87a7i9ww82.fsf@atlas.engineer> <87y35ft1p7.fsf@ambrevar.xyz> <87imwgsh64.fsf@gnu.org> 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]:49202) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h6MTg-0007tl-8d for bug-guix@gnu.org; Tue, 19 Mar 2019 17:40:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h6MTe-0003pa-7r for bug-guix@gnu.org; Tue, 19 Mar 2019 17:40:55 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:37442) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h6MRq-00032L-7D for bug-guix@gnu.org; Tue, 19 Mar 2019 17:40:53 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h6MRp-0006IU-Sm for bug-guix@gnu.org; Tue, 19 Mar 2019 17:39:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87imwgsh64.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: Pierre Neidhardt , 27217@debbugs.gnu.org, Jelle Licht Ludovic Court=C3=A8s writes: >> I'm suggesting those following steps: >> >> - Write the package definition generator. We can take inspiration from >> opam.scm, it seems to be well written and very similar. >> `texlive-fetch' is already aligned with `opam-fetch'. >> >> For testing, we can try to recreate a simple package definition. >> texlive-latex-xcolor for instance. >> There is an immediate difference already: the name generated by the im= porter >> will be texlive-xcolor and not texlive-latex-xcolor. >> >> - Write texlive-fetch so that we can write definitions with multiple >> directories. >> >> - Update the texlive-build-system to accommodate the importer. For inst= ance, we >> will probably have to build fonts automatically. We will also have to= be >> smart about the files that need to be generated, and those that need t= o be discarded. >> >> - Write an updater (again, following opam.scm, should be trivial). >> >> I'll get started with the first step today. Let me know what you think! > > So TeX Live packages would use =E2=80=98texlive-fetch=E2=80=99 instead of= =E2=80=98svn-fetch=E2=80=99 or > similar, right? > > If that=E2=80=99s the case, then merely computing the derivation of one o= f these > would require fetching the tldb database, which would be problematic. > Is this correct? I think there has been a misunderstanding here. Pierre seems to be using the name =E2=80=9Ctexlive-fetch=E2=80=9D for two different things. A= s it stands it is not a source code downloader. It is a procedure that extracts a package=E2=80=99s information from the parsed plain text database. The thing I proposed some days ago (also named =E2=80=9Ctexlive-fetch=E2=80= =9D) would be a variant of =E2=80=9Csvn-fetch=E2=80=9D that supports more than one locati= on in the target SVN repository so that disjoint subsets of the SVN tree can be downloaded at the same time. This is unrelated. The extraction of information from the plain text database (which is included with =E2=80=9Ctexlive-bin=E2=80=9D) is done =E2=80=9Coffline=E2=80= =9D when using the importer, i.e. when generating package definitions. -- Ricardo