Why is `openin_any = p` restricting access to packages in TEXMFDIST?
David Carlisle
d.p.carlisle at gmail.com
Thu Sep 24 11:23:41 CEST 2020
I temporary workaround until the new binaries are available would be to use
\expandafter\let\csname file_input:n\endcsname\input
\documentclass{article}
\usepackage{xparse}
\begin{document}
\end{document}
this reverts to the non-expandable \openin test to check a file exists so
could fail in some theoretical contexts but it works in this real context,
so a good workaround for now, I think.
On Thu, 24 Sep 2020 at 10:21, Adrian <adrian at planetcoding.net> wrote:
> Great!
>
> Any chance you could try with this "real" tex file as well (just in case
> there's
> anything else that triggered the error)?
> https://fd.aeum.net/latex-test.tar
>
> > On 2020/09/24 17:54, Adrian wrote:
> >> Does that commit restore the old behavior about being able to use
> packages even
> >> with `openin_any = p`?
>
> > Yes, I confirmed that
>
> > \documentclass{article}
> > \usepackage{xparse}
> > \begin{document}
> > \end{document}
>
> > works for latex in the case openin_any = p.
>
> > It is necessary to rebuild binaries with the new sources.
>
> > Best,
> > Akira
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/tex-live/attachments/20200924/1bdd23bb/attachment.html>
More information about the tex-live
mailing list.