From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#35780: [PATCH] attempt to fix polyglossia Date: Sat, 18 May 2019 05:50:13 +0200 Message-ID: <87y334ctfu.fsf@elephly.net> References: <20190517165152.GA5797@spica.localdomain> <20190517212351.8855-1-josh@inv.alid.pw> 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]:54710) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hRqOC-00061c-65 for bug-guix@gnu.org; Fri, 17 May 2019 23:52:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hRqOB-0004wk-5m for bug-guix@gnu.org; Fri, 17 May 2019 23:52:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:45903) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hRqOA-0004wP-Iw for bug-guix@gnu.org; Fri, 17 May 2019 23:52:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hRqOA-0000AY-A2 for bug-guix@gnu.org; Fri, 17 May 2019 23:52:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <20190517212351.8855-1-josh@inv.alid.pw> 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: Josh Holland Cc: 35780@debbugs.gnu.org Hi Josh, > I had a quick look into fixing this myself, and made a little bit > of progress. Not being that familiar with how things work yet, > I'm going on what I can guess by looking at gnu/packages/tex.scm, > guix/build-system/texlive.scm and guix/build/texlive-build-system.scm > so I may well be misinterpreting some things. > > The source for polyglossia comes in a single file, polyglossia.dtx. > The README embedded within it says to extract the files by running > xetex or luatex on it. I tried to convince the build system to do > this by this patch, which may or may not have been the right approach. Thanks for giving it a try. The build system works on =E2=80=9Cins=E2=80= =9D files by default. I guess it should try =E2=80=9Cdtx=E2=80=9D files as well. > It does at least get a new error: > > Generating file(s) ../README > ! I can't write on file `../README.tex'. > > It appears to be trying to write its README file to the directory above > the build directory, which is failing. Is there a way to make this > directory writeable, or to stop the build system from trying to generate > the README there? We can patch the dtx file in a build phase and replace =E2=80=9C../README= =E2=80=9D with just =E2=80=9CREADME=E2=80=9D. We can=E2=80=99t write to the parent of the= build directory, and extracting everything a level deeper seems wrong. What do you think? -- Ricardo