unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>, guix-devel@gnu.org
Subject: Re: LaTeX packaging policy
Date: Fri, 06 Jan 2023 17:30:03 +0100	[thread overview]
Message-ID: <87v8ljhbhw.fsf@gmail.com> (raw)
In-Reply-To: <87k02hj9fb.fsf@jpoiret.xyz>

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


      parent reply	other threads:[~2023-01-06 16:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 12:03 LaTeX packaging policy Josselin Poiret
2023-01-03  9:05 ` Ludovic Courtès
2023-01-03  9:13   ` Nguyễn Gia Phong
2023-01-03 21:11     ` Ludovic Courtès
2023-01-04  7:11       ` Reza Housseini
2023-01-04  7:22         ` Nguyễn Gia Phong
2023-01-04 10:26           ` Ludovic Courtès
2023-01-06 16:30 ` Simon Tournier [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=87v8ljhbhw.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=dev@jpoiret.xyz \
    --cc=guix-devel@gnu.org \
    /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).