From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Kolen Cheung
<christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: GitHub Releases naming convention for Linux builds
Date: Fri, 04 Oct 2019 21:59:56 -0700 [thread overview]
Message-ID: <m2lftzg52r.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <be3c23fb-d627-4260-8687-f2ba1cf4b5a3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
I think it makes sense to use
pandoc-2.7.3-linux-amd64.tar.gz
but keep
pandoc-2.7.3-1-amd64.deb
since the deb is clearly linux; this is the style of
filename generally used for debs.
Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Currently the filename convention for the Linux zip archive
> is pandoc-2.7.3-linux.tar.gz, I suppose it is for amd64 arch? And the deb
> build is pandoc-2.7.3-1-amd64.deb, may be it is better to release them in a
> uniform naming convention as pandoc-2.7.3-linux-amd64.tar.gz,
> pandoc-2.7.3-1-linux-amd64.deb in the future? This is in line with the
> naming convention used in the Windows builds too.
>
> --
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/be3c23fb-d627-4260-8687-f2ba1cf4b5a3%40googlegroups.com.
next prev parent reply other threads:[~2019-10-05 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 20:16 Kolen Cheung
[not found] ` <be3c23fb-d627-4260-8687-f2ba1cf4b5a3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-05 4:56 ` John MacFarlane
2019-10-05 4:59 ` John MacFarlane [this message]
[not found] ` <m2lftzg52r.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-10-05 16:59 ` Windows testing requested John MacFarlane
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=m2lftzg52r.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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).