From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] texlive: make tlmgr work.
Date: Sun, 16 Aug 2020 04:28:38 +0200 [thread overview]
Message-ID: <20200816022838.aA7zDBmiZpHINDRUn_tC9wOozZlzMq6pMMPjchcpW1U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24300@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
New review comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/24300#discussion_r471055630
Comment:
> There is no gurantee it will be /usr.
Why not? We are the ones putting the script there.
> % Redistributors will probably want $SELFAUTODIR/share, i.e., /usr/share.
Doesn't this mean that this is a known usecase, and that they are ready for it? It feels like it should require config options instead of patching :/
Overall, a wrapper script is better than patching, if only because it avoids rebasing for a new release.
next prev parent reply other threads:[~2020-08-16 2:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 23:41 [PR PATCH] " fosslinux
2020-08-15 23:42 ` [PR PATCH] [Updated] " fosslinux
2020-08-16 1:13 ` [PR REVIEW] " ericonr
2020-08-16 1:26 ` fosslinux
2020-08-16 1:38 ` fosslinux
2020-08-16 2:28 ` ericonr [this message]
2020-08-16 2:52 ` fosslinux
2020-08-16 2:53 ` [PR PATCH] [Updated] " fosslinux
2020-08-16 2:54 ` [PR REVIEW] " ericonr
2020-08-16 2:55 ` ericonr
2020-08-16 4:07 ` ericonr
2020-08-16 4:10 ` fosslinux
2020-08-16 4:12 ` ericonr
2020-08-16 4:12 ` ericonr
2020-08-16 4:13 ` ericonr
2020-08-16 4:14 ` fosslinux
2020-08-16 4:31 ` ericonr
2020-08-16 4:36 ` [PR PATCH] [Updated] " fosslinux
2020-08-16 5:25 ` [do not merge] texlive: make tlmgr work and split libsynctex fosslinux
2020-08-16 5:29 ` ericonr
2020-08-16 5:30 ` ericonr
2020-08-16 5:36 ` fosslinux
2020-08-16 8:04 ` fosslinux
2020-08-16 8:07 ` [PR PATCH] [Updated] " fosslinux
2020-08-17 13:48 ` [PR PATCH] [Closed]: " 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=20200816022838.aA7zDBmiZpHINDRUn_tC9wOozZlzMq6pMMPjchcpW1U@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).