From: Ricardo Wurmus <rekado@elephly.net>
To: Josh Holland <josh@inv.alid.pw>
Cc: 35780@debbugs.gnu.org
Subject: bug#35780: [PATCH] attempt to fix polyglossia
Date: Sat, 18 May 2019 05:50:13 +0200 [thread overview]
Message-ID: <87y334ctfu.fsf@elephly.net> (raw)
In-Reply-To: <20190517212351.8855-1-josh@inv.alid.pw>
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 “ins” files by
default. I guess it should try “dtx” 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 “../README” with
just “README”. We can’t write to the parent of the build directory, and
extracting everything a level deeper seems wrong.
What do you think?
--
Ricardo
next prev parent reply other threads:[~2019-05-18 3:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 16:51 bug#35780: texlive-latex-polyglossia package empty Josh Holland
2019-05-17 21:23 ` bug#35780: [PATCH] attempt to fix polyglossia Josh Holland
2019-05-18 3:50 ` Ricardo Wurmus [this message]
2019-06-21 15:40 ` Josh Holland
2022-05-14 5:22 ` bug#35780: texlive-latex-polyglossia package empty Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y334ctfu.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35780@debbugs.gnu.org \
--cc=josh@inv.alid.pw \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.