Github messages for voidlinux
 help / color / mirror / Atom feed
From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Texlive 2023
Date: Fri, 12 Jan 2024 15:23:13 +0100	[thread overview]
Message-ID: <20240112142313.rahUX_M1j4TUG71paAAvDniDtcSivR1YJTOzUcjK7YI@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: 1977 bytes --]

New comment by tornaria on void-packages repository

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

Comment:
> Thanks; applied those two.
> 
> Re: texdoc, I'm not certain of the best way to attack that at this point. We can't include the docs in the main package - they're HUGE. They don't seem to be included in any tarball. This is something I'd prefer to address in a follow up PR.

I think the docs are (optionally?) produced when each TL package is built, and placed in `$TEXMFDIST/doc/`. I think arch creates these TL packages without the documentation (each `*.xz` file inside `texlive-core-2023.66587-src.zip` and friends is one TL package) and makes this zip files with collections of packages.

In spite of the name, I don't think these files `texlive-core-2023.66587-src.zip` are texlive sources, and I don't think the arch package uses those, rather something more like `texlive-20230313-texmf.tar.xz`. That one file seems to contain everything, source, runtime and documentation for all the collections together. Then there's `texlive-20230311-tlpdb-full.tar.gz` which contains the database of installed files; arch seems to parse the database to split the texmf runtime files into collections, and I think all the documentation goes together in a single package (but documentation could also be split by collections).

TL;DR
 - the docs are included in `texlive-20230313-texmf.tar.xz`
 - the database with meta information of all those files is in `texlive-20230311-tlpdb-full.tar.gz`
 - maybe it's possible to eventually transition to using those files to generate all collections and documentation of collections (and also ship the database which I think is needed by texdoc)


Another note: I think texlive expects the `tlpkg` directory to be placed in `/usr/share/tlpkg` instead of `/usr/share/texmf-dist/tlpkg`. Simple way to fix this is to make a symlink, and I think doing this gets rid of some patches here.

  parent reply	other threads:[~2024-01-12 14:23 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 [this message]
2024-01-12 23:04 ` fosslinux
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=20240112142313.rahUX_M1j4TUG71paAAvDniDtcSivR1YJTOzUcjK7YI@z \
    --to=tornaria@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).