From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: tlmgr not working
Date: Sat, 15 Aug 2020 20:17:37 +0200 [thread overview]
Message-ID: <20200815181737.uutZAZ_2raMm6muyZkNBqGHwoINAJlVrLatlAyz-WTo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24013@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/24013#issuecomment-674431797
Comment:
We do need to update the docs https://github.com/void-linux/void-docs/issues/371
`texlive-bin` uses a build that's distributed by tex live folks, as I understand it. The new `texlive` packages are built by us, instead.
> (I would actually really, really like zathura to have libsynctex support but hey, that's another issue)
Now that we have actual `texlive` packages, this is a possibility. You should open an in issue requesting it or make a PR adding it.
next prev parent reply other threads:[~2020-08-15 18:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24013@inbox.vuxu.org>
2020-08-06 17:20 ` ericonr
2020-08-15 17:55 ` chilledfrogs
2020-08-15 18:17 ` ericonr [this message]
2020-08-15 21:35 ` fosslinux
2020-08-15 23:44 ` fosslinux
2020-08-17 13:48 ` [ISSUE] [CLOSED] " ahesford
2020-08-17 17:08 ` chilledfrogs
2020-08-17 17:13 ` ericonr
2020-08-17 17:18 ` chilledfrogs
2020-08-17 17:19 ` chilledfrogs
2020-08-17 17:21 ` ericonr
2020-08-17 17:21 ` chilledfrogs
2020-08-17 17:22 ` chilledfrogs
2020-08-17 17:22 ` ericonr
2020-08-17 17:23 ` chilledfrogs
2020-08-17 17:58 ` chilledfrogs
2020-08-17 23:13 ` fosslinux
2020-08-17 23:23 ` ahesford
2021-01-21 0:17 ` fosslinux
2021-01-21 0:49 ` [ISSUE] [CLOSED] " ahesford
2022-01-17 11:05 ` scheckley
2022-01-17 11:10 ` scheckley
2022-09-20 17:39 ` dexgs
2022-11-02 11:07 ` narodnik
2022-11-02 11:25 ` ahesford
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=20200815181737.uutZAZ_2raMm6muyZkNBqGHwoINAJlVrLatlAyz-WTo@z \
--to=ericonr@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).