Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Package request: libsynctex(-devel)
Date: Thu, 17 Oct 2019 18:17:37 +0200	[thread overview]
Message-ID: <20191017161737.7QNx3nCKvAx_xRYojp5PGCmmdmsayFp2Q_ACp7pKxwI@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: 1245 bytes --]

New comment by xtraeme on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-543251184

Comment:
👌

El jue., 17 oct. 2019 18:14, stuart-little <notifications@github.com>
escribió:

> And actually, there's no reason why you wouldn't make your own xbps
> package out of the arch libsynctex binary too, for easier package
> management. I tried it just now:
>
> Once you untar the archive
> <https://www.archlinux.org/packages/extra/x86_64/libsynctex/> to some
> <dir> just run
>
> # xbps-create -n libsynctex-2019.51075_1 -s "libsynctex" -A x86_64 <dir>
>
> and then install the resulting package with xdowngrade, as in the previous
> post
> <https://github.com/void-linux/void-packages/issues/5602#issuecomment-542799893>
> .
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/issues/5602?email_source=notifications&email_token=AAGR7KNK5PQFXRODHHUJRH3QPCFOZA5CNFSM4GJI4BA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBQVMWI#issuecomment-543250009>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAGR7KO3OHAY3N7ISO6QEBLQPCFOZANCNFSM4GJI4BAQ>
> .
>


  parent reply	other threads:[~2019-10-17 16:17 UTC|newest]

Thread overview: 38+ 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:07 ` voidlinux-github
2019-10-16 17:18 ` voidlinux-github
2019-10-17 16:14 ` voidlinux-github
2019-10-17 16:17 ` voidlinux-github [this message]
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 ` [ISSUE] [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=20191017161737.7QNx3nCKvAx_xRYojp5PGCmmdmsayFp2Q_ACp7pKxwI@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).