From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: bug#27217: texlive is too big Date: Thu, 10 Jan 2019 19:56:16 +0100 Message-ID: <87o98ocpf3.fsf@ambrevar.xyz> 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> <87muo84jcu.fsf@elephly.net> <87ftu04i37.fsf@ambrevar.xyz> <87k1jc4hmf.fsf@elephly.net> <87ef9k4d6i.fsf@ambrevar.xyz> <87imyw4a9i.fsf@elephly.net> 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]:52065) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ghfVn-0006nz-Cp for bug-guix@gnu.org; Thu, 10 Jan 2019 13:57:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ghfVm-0001gi-Ny for bug-guix@gnu.org; Thu, 10 Jan 2019 13:57:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:54932) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ghfVm-0001gX-Ka for bug-guix@gnu.org; Thu, 10 Jan 2019 13:57:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ghfVm-00024V-BT for bug-guix@gnu.org; Thu, 10 Jan 2019 13:57:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87imyw4a9i.fsf@elephly.net> 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: Ricardo Wurmus Cc: 27217@debbugs.gnu.org > Yes, the SVN repo does include generated files. That=E2=80=99s not great= , but > we can choose to ignore those files (as we do in other projects). And the builder should take care not to discard .sty / .cls files that are = not going to be generated. I believe that in all cases the basename remains the same between .dtx/.ins and .sty/.cls. Then it's easy to know which one to = keep and which one to discards. So what do you think of the tlpdb approach for a new tex-build-system?