Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: texlive: fix tlmgr.
Date: Mon, 04 Jan 2021 22:51:42 +0100	[thread overview]
Message-ID: <20210104215142.L1pgzl9UzJKGt9a_NlJsx2-84BnffvWCMp6-R5ujUrE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27653@inbox.vuxu.org>

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

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/27653#issuecomment-754242340

Comment:
> I don't see any way in which that is "actively hostile to packaging".

I meant the specific new package you're creating, since it doesn't exist as a versioned thing.

Can you install packages with `tlmgr` onto any arch, or does it work only for glibc stuff? Because if it only works for glibc, I'm okay with moving it to texlive-bin entirely. Still, a minimally working program that allows you to control settings and stuff can be nice, so we might just have to make do... I assume we can't fake a tpldb, just for tlmgr to kind of work?

  parent reply	other threads:[~2021-01-04 21:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 11:03 [PR PATCH] " fosslinux
2021-01-04 11:14 ` texlive: fix tlmgr. [ci skip] fosslinux
2021-01-04 11:16 ` [PR PATCH] [Updated] texlive: fix tlmgr fosslinux
2021-01-04 12:48 ` ericonr
2021-01-04 21:23 ` fosslinux
2021-01-04 21:51 ` ericonr [this message]
2021-01-05  8:12 ` [PR PATCH] [Updated] " fosslinux
2021-01-05  8:13 ` fosslinux
2021-01-06  4:34 ` ericonr
2021-01-06  4:57 ` [PR REVIEW] " ericonr
2021-01-06  8:38 ` [PR PATCH] [Updated] " fosslinux
2021-01-08 17:35 ` [PR PATCH] [Merged]: " ericonr

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=20210104215142.L1pgzl9UzJKGt9a_NlJsx2-84BnffvWCMp6-R5ujUrE@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).