Github messages for voidlinux
 help / color / mirror / Atom feed
From: fosslinux <fosslinux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Texlive 2023
Date: Sat, 13 Jan 2024 00:04:34 +0100	[thread overview]
Message-ID: <20240112230434.W91FVKebD6NZAtFMME5pVsIqwI0wNbbGqzgRD8w0pRY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47130@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 770 bytes --]

New comment by fosslinux on void-packages repository

https://github.com/void-linux/void-packages/pull/47130#issuecomment-1890109749

Comment:
Hmm, alright.

I'll have a bit of a closer look at arch's texlive packages, and a couple of other distributions.
If it is appropriate to do so, I'll have a look at the possibility of taking collections straight from upstream, rather than from Arch.

Previously, the consensus was that shipping tlpdb didn't really make any sense since tlmgr system wide is unsupported. But that might not be quite true. Perhaps tlpdb should be shipped - with the intention that it is still a package managed file and is not changed by the user.

(This is still something I'd prefer to address after this PR, let's get this merged first)

  parent reply	other threads:[~2024-01-12 23:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09  3:57 [PR PATCH] WIP: " fosslinux
2023-12-21  0:55 ` [PR PATCH] [Updated] " fosslinux
2023-12-29  4:58 ` fosslinux
2023-12-29  5:00 ` fosslinux
2024-01-06 18:23 ` tornaria
2024-01-06 22:26 ` tornaria
2024-01-06 22:26 ` tornaria
2024-01-12  6:08 ` fosslinux
2024-01-12  6:10 ` [PR PATCH] [Updated] " fosslinux
2024-01-12 14:23 ` tornaria
2024-01-12 23:04 ` fosslinux [this message]
2024-02-08  7:06 ` [PR PATCH] [Updated] " fosslinux
2024-02-08 11:23 ` [PR PATCH] [Merged]: " ahesford
2024-02-29 21:43 ` dkwo

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=20240112230434.W91FVKebD6NZAtFMME5pVsIqwI0wNbbGqzgRD8w0pRY@z \
    --to=fosslinux@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).