[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LaTeX packaging policy
From: |
Simon Tournier |
Subject: |
Re: LaTeX packaging policy |
Date: |
Fri, 06 Jan 2023 17:30:03 +0100 |
Hi,
On Sat, 24 Dec 2022 at 13:03, Josselin Poiret <dev@jpoiret.xyz> wrote:
> While using a bit of LaTeX recently, I've noticed some packages don't
> work "out-of-the-box", at least on LuaLaTeX, and need some additional
> propagated inputs. Examples would be babel-french needing scalefnt,
> fontspec needing luaotfload, or hyperref needing stringenc. Is there
> any established policy for what propagated-inputs need to be included in
> package definitions? Should we add some LaTeX specific packaging
> guidelines in the manual, like for Python or Rust (the former is
> outdated by the way, mentioning Python 2 packages).
All the inputs are they required as propagated-inputs? Or only some?
Maybe it could be worth to fix the broken packages (the examples above)
and see if a pattern emerge for writing down a policy.
Or maybe, we could propagate all the inputs since TeX can be considered
as stable enough for minimizing the clash of versions.
Cheers,
simon
- Re: LaTeX packaging policy,
Simon Tournier <=