unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Josh Holland <josh@inv.alid.pw>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, 35780@debbugs.gnu.org
Subject: bug#35780: [PATCH] attempt to fix polyglossia
Date: Fri, 21 Jun 2019 16:40:06 +0100	[thread overview]
Message-ID: <20190621154006.GA7268@sirius.localdomain> (raw)
In-Reply-To: <87y334ctfu.fsf@elephly.net>

Hi,

(CCing guix-devel because I'm confused about this and more eyes can't
hurt)

On Sat, May 18, 2019 at 05:50:13AM +0200, Ricardo Wurmus wrote:
> Thanks for giving it a try.  The build system works on “ins” files by
> default.  I guess it should try “dtx” files as well.

Should this be a patch to the build-system?  Although maybe it's not
that simple: https://ctan.org/texarchive/macros/xetex/latex/polyglossia
lists four files, incuding an "ins" file.

> We can patch the dtx file in a build phase and replace “../README” with
> just “README”.

I tried patching the README path as Ricardo suggested.  This got
somewhere, complaining of missing fonts, so I added texlive-fonts-cm
to native-inputs.  With both these changes, the build now fails while
trying to build example-thai.tex, and the errors appear to indicate
trying to build a LaTeX file with plain TeX:

Processing file polyglossia.dtx (example-thai.tex) -> example-thai.tex
File polyglossia.dtx ended by \endinput.
Lines  processed: 11224
Comments removed: 1600
Comments  passed: 215
Codelines passed: 9209

! Undefined control sequence.
l.209 \documentclass
                  [11pt]{ltxdoc}
! Undefined control sequence.
l.210 \usepackage
               {color}
! Undefined control sequence.
l.211 \usepackage
               {xspace,fancyvrb}
! Undefined control sequence.
l.212 \usepackage
               [neverdecrease]{paralist}
! Undefined control sequence.
l.213 \definecolor
                {myblue}{rgb}{0.02,0.04,0.48}
! Undefined control sequence.
l.214 \definecolor
                {lightblue}{rgb}{0.61,.8,.8}
! Undefined control sequence.
l.215 \definecolor
                {myred}{rgb}{0.65,0.04,0.07}
! Undefined control sequence.

(and more...)

I'm not that familiar with the intricacies of properly building TeXLive
from source, but the difference between the file list on CTAN and what
comes from the Subversion repo via texlive-ref smells fishy to me.  If I
manually run any permutation of  `{xe,lua}tex polyglossia.{ins,dtx}`
it mostly seems to build OK, but to my surprise no polyglossia.sty
is produced!  There's no actual build instructions in the README or the
polyglossia.pdf, so I'm rather lost here.

Thanks,

-- 
Josh Holland

       reply	other threads:[~2019-06-21 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190517165152.GA5797@spica.localdomain>
     [not found] ` <20190517212351.8855-1-josh@inv.alid.pw>
     [not found]   ` <87y334ctfu.fsf@elephly.net>
2019-06-21 15:40     ` Josh Holland [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190621154006.GA7268@sirius.localdomain \
    --to=josh@inv.alid.pw \
    --cc=35780@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).