From: spencernursiapress@nursiapress.com
To: 67723@debbugs.gnu.org
Subject: [bug#67723] [PATCH 0/2] Fix the texlive-poetry package
Date: Sat, 9 Dec 2023 19:54:38 -0000 [thread overview]
Message-ID: <ae42b8be7162c644f7204684a992aeec.squirrel@p110.lithium.hosting> (raw)
In-Reply-To: <cover.1702087317.git.spencer@nursiapress.com>
Hi Nicolas,
I appreciate the quick response. I've read through the conversation on issue
67660 and understand your concerns, but can't say that I entirely agree. I am
aware that it would be a substantial manual burden to fix the potentially
hundreds of impacted packages. However, from an end-user perspective, those
packages are currently broken. I think it is completely valid for the Guix
project to not want to take on the burden of managing those dependencies,
however I fail to see the utility in offering individual packages in that
case.
On the other issue you had mentioned the idea of having package collections.
How do you envision that working in practice? For example, if I wanted to
create a collection for typesetting poetry it seems a little arbitrary which
packages I would choose to include.
I am a frequent user of the Tex ecosystem and would like to improve it in
Guix. Currently it seems that the only realistic way to use Tex is to install
the entirety of texlive, which isn't any different than what I would do on
any
other distro.
Best,
Spencer
next prev parent reply other threads:[~2023-12-10 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 2:04 [bug#67723] [PATCH 0/2] Fix the texlive-poetry package Spencer King
2023-12-09 3:03 ` [bug#67723] [PATCH 1/2] gnu: texlive-imakeidx: Fix inputs Spencer King
2023-12-09 3:03 ` [bug#67723] [PATCH 2/2] gnu: texlive-poetry: " Spencer King
2023-12-09 14:21 ` [bug#67723] [PATCH 0/2] Fix the texlive-poetry package Nicolas Goaziou via Guix-patches via
2023-12-09 19:54 ` spencernursiapress [this message]
2023-12-10 10:46 ` Nicolas Goaziou via Guix-patches via
2024-10-31 13:57 ` [bug#67723] texlive-poetry package issues Steve George
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae42b8be7162c644f7204684a992aeec.squirrel@p110.lithium.hosting \
--to=spencernursiapress@nursiapress.com \
--cc=67723@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.