unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Expanding texlive-iftex to include all sty files
Date: Tue, 27 Oct 2020 11:36:32 +0100	[thread overview]
Message-ID: <87tuug0xcf.fsf@elephly.net> (raw)
In-Reply-To: <87k0vcoxlw.fsf@ambrevar.xyz>


Pierre Neidhardt <mail@ambrevar.xyz> writes:

> Hi!
>
>> The current texlive-iftex recipe only includes iftex.sty, despite 
>> the upstream https://ctan.org/pkg/iftex also including 
>> if{e,lua,v,xe}tex.sty files.  Is there a way to expand the recipe 
>> to include those additional files?
>> 
>> I think this should be accomplished just by including the files' 
>> paths in the third argument to `simple-texlive-package' in the 
>> recipe's definition, but the recipe's version would also need to 
>> be bumped and I don't see any examples of how to do so for TeX 
>> recipes.
>
> Recently Ricardo was fixing a few texlive packages I believe.
>
> Ricardo, do you know if this has been fixed somehow?

It doesn’t seem to be a problem according to texlive.tlpd:

--8<---------------cut here---------------start------------->8---
name iftex
category Package
revision 29654
shortdesc Am I running under pdfTeX, XeTeX or LuaTeX?
longdesc The package, which works both for Plain TeX and for LaTeX,
longdesc defines the \ifPDFTeX, \ifXeTeX, and \ifLuaTeX conditionals for
longdesc testing which engine is being used for typesetting. The package
longdesc also provides the \RequirePDFTeX, \RequireXeTeX, and
longdesc \RequireLuaTeX commands which throw an error if pdfTeX, XeTeX
longdesc or LuaTeX (respectively) is not the engine in use.
docfiles size=10
 texmf-dist/doc/generic/iftex/README details="Readme"
 texmf-dist/doc/generic/iftex/iftex.pdf details="Package documentation"
 texmf-dist/doc/generic/iftex/iftex.tex
runfiles size=1
 texmf-dist/tex/generic/iftex/iftex.sty
catalogue-also ifpdf ifluatex
catalogue-contact-bugs https://github.com/bidi-tex/iftex/issues
catalogue-contact-repository https://github.com/bidi-tex/iftex
catalogue-ctan /macros/latex/contrib/iftex
catalogue-date 2018-11-28 19:50:39 +0100
catalogue-license lppl1.3
catalogue-topics env-query
catalogue-version 0.2
--8<---------------cut here---------------end--------------->8---

According to texlive.tlpdb we should add a separate package for
ifluatex…

--8<---------------cut here---------------start------------->8---
name ifluatex
category Package
revision 49285
shortdesc Provides the \ifluatex switch
longdesc The package looks for LuaTeX regardless of its mode and
longdesc provides the switch \ifluatex; it works with Plain TeX or
longdesc LaTeX. The package is part of the oberdiek bundle.
docfiles size=33
 texmf-dist/doc/latex/oberdiek/ifluatex.pdf details="Package documentation"
 texmf-dist/doc/latex/oberdiek/test/ifluatex-test1.tex
 texmf-dist/doc/latex/oberdiek/test/ifluatex-test2.tex
 texmf-dist/doc/latex/oberdiek/test/ifluatex-test3.tex
srcfiles size=7
 texmf-dist/source/latex/oberdiek/ifluatex.dtx
runfiles size=2
 texmf-dist/tex/generic/oberdiek/ifluatex.sty
catalogue-ctan /macros/latex/contrib/oberdiek/ifluatex.dtx
catalogue-date 2018-01-06 12:14:59 +0100
catalogue-license lppl1.3
catalogue-topics env-query
catalogue-version 1.4
--8<---------------cut here---------------end--------------->8---

…and ifetex:

--8<---------------cut here---------------start------------->8---
name ifetex
category Package
revision 47231
shortdesc Provides \ifetex switch
longdesc The package provides the switch \ifetex which indicates whether
longdesc e-TeX is available or not. The package can be loaded as LaTeX
longdesc package using \usepackage{ifetex} or in plain TeX using \input
longdesc ifetex. In either case it aborts silently if the \ifetex macro
longdesc is already defined. The package's test is whether \eTeXversion
longdesc is defined as a primitive; if it is, the package assumes e-TeX
longdesc features are available.
docfiles size=37
 texmf-dist/doc/latex/ifetex/README details="Readme"
 texmf-dist/doc/latex/ifetex/ifetex.pdf details="Package documentation"
srcfiles size=3
 texmf-dist/source/latex/ifetex/ifetex.dtx
 texmf-dist/source/latex/ifetex/ifetex.ins
runfiles size=2
 texmf-dist/tex/latex/ifetex/ifetex.sty
 texmf-dist/tex/plain/ifetex/ifetex.tex
catalogue-contact-bugs https://bitbucket.org/martin_scharrer/ifetex/issues
catalogue-contact-home https://bitbucket.org/martin_scharrer/ifetex/
catalogue-contact-repository https://bitbucket.org/martin_scharrer/ifetex/src
catalogue-ctan /macros/latex/contrib/ifetex
catalogue-date 2018-03-31 21:11:18 +0200
catalogue-license lppl1.3
catalogue-topics env-query
catalogue-version 1.2a
--8<---------------cut here---------------end--------------->8---


-- 
Ricardo


      reply	other threads:[~2020-10-27 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19 18:11 Expanding texlive-iftex to include all sty files LaFreniere, Joseph
2020-10-27  8:56 ` Pierre Neidhardt
2020-10-27 10:36   ` Ricardo Wurmus [this message]

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=87tuug0xcf.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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.
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).