From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Package request: libsynctex(-devel)
Date: Sun, 16 Aug 2020 03:21:21 +0200 [thread overview]
Message-ID: <20200816012121.oYmNzzmN3Bf8sO18ChSuTegly57Xrw3eAK5vws8Cu8I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
Closed issue by xaltsc on void-packages repository
https://github.com/void-linux/void-packages/issues/5602
Description:
Providing this package would likely require to rethink how Void offers LaTeX, but it's such a pain somewhere in your body to work on >100 without having backward and forward search on your favourite pdf reader...
References:
[1] https://github.com/voidlinux/void-packages/issues/7022
[2] @svenper has a nice template here: https://gitlab.com/svenper/home-bin/tree/master/patches/templates, but I couldn't manage to build it.
[3] Rémy Oudompheng has a pretty straightforward PKGBUILD on the AUR (https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/texlive-bin) but again to change the way VoidLinux offers TexLive.
prev parent reply other threads:[~2020-08-16 1:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
2019-10-16 17:18 ` voidlinux-github
2019-10-17 16:14 ` voidlinux-github
2019-10-17 16:17 ` voidlinux-github
2019-10-17 16:43 ` voidlinux-github
2020-01-12 12:05 ` voidlinux-github
2020-01-12 12:06 ` voidlinux-github
2020-01-12 13:02 ` voidlinux-github
2020-01-12 13:02 ` voidlinux-github
2020-01-12 13:04 ` voidlinux-github
2020-01-12 13:09 ` voidlinux-github
2020-01-12 16:09 ` voidlinux-github
2020-01-12 16:23 ` voidlinux-github
2020-01-12 16:28 ` voidlinux-github
2020-01-12 16:45 ` voidlinux-github
2020-01-12 16:51 ` voidlinux-github
2020-01-12 16:52 ` voidlinux-github
2020-01-12 17:29 ` voidlinux-github
2020-01-12 17:30 ` voidlinux-github
2020-01-12 17:32 ` voidlinux-github
2020-01-12 20:37 ` voidlinux-github
2020-01-12 23:14 ` voidlinux-github
2020-01-12 23:16 ` voidlinux-github
2020-01-12 23:23 ` voidlinux-github
2020-01-12 23:25 ` voidlinux-github
2020-01-13 0:34 ` voidlinux-github
2020-01-13 10:52 ` voidlinux-github
2020-01-13 10:52 ` voidlinux-github
2020-01-13 10:53 ` voidlinux-github
2020-01-13 18:12 ` voidlinux-github
2020-03-13 15:01 ` svenper
2020-04-04 16:20 ` svenper
2020-04-07 13:16 ` svenper
2020-04-15 15:57 ` svenper
2020-04-15 19:35 ` svenper
2020-04-20 2:48 ` svenper
2020-08-15 23:44 ` fosslinux
2020-08-16 1:21 ` ahesford [this message]
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=20200816012121.oYmNzzmN3Bf8sO18ChSuTegly57Xrw3eAK5vws8Cu8I@z \
--to=ahesford@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).