From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin-apps@cygwin.com
Subject: [ITP] cmark: CommonMark parsing and rendering library
Date: Sun, 21 Jan 2018 23:31:00 -0000 [thread overview]
Message-ID: <dcd1a708-511e-cf6a-088f-51e1bb81a715@tiscali.co.uk> (raw)
'cmark' is a prerequisite for the latest version of mkvtoolnix-gui.
'cmark' is found in most major distros - see https://pkgs.org/download/cmark
The library does not have a 'so' version. I've had a look to see how the
major distros cope with this, and IMHO the most sensible is found in
openSuse. The approach used there is to append the version number to the
library package name. However, if anyone has a better way to cope with
the lack of 'so' number then I'd be very interested.
Many thanks for taking a look,
Dave.
# x86
BASEURL=https://www.dropbox.com/s
mkdir -p x86/release/cmark
pushd x86/release/cmark
wget ${BASEURL}/4ajzely0nv1bqbc/cmark-0.28.3-1-src.tar.xz
wget ${BASEURL}/mftgz8eztuc468y/cmark-0.28.3-1.tar.xz
wget ${BASEURL}/b6b05lalw965ce6/cmark-0.28.3-1.hint
mkdir cmark-debuginfo cmark-devel libcmark0_28_3
cd cmark-debuginfo
wget ${BASEURL}/gqyx9k9y0qhcq3p/cmark-debuginfo-0.28.3-1.hint
wget ${BASEURL}/speysbhush1lfpa/cmark-debuginfo-0.28.3-1.tar.xz
cd ../cmark-devel
wget ${BASEURL}/7a3jp8ic8vzeu6c/cmark-devel-0.28.3-1.hint
wget ${BASEURL}/pjhjbuikst91nau/cmark-devel-0.28.3-1.tar.xz
cd ../libcmark0_28_3
wget ${BASEURL}/a5a6du0wso3lxwg/libcmark0_28_3-0.28.3-1.hint
wget ${BASEURL}/qcm34pxgamxrygb/libcmark0_28_3-0.28.3-1.tar.xz
popd
# x86_64
BASEURL=https://www.dropbox.com/s
mkdir -p x86_64/release/cmark
pushd x86_64/release/cmark
wget ${BASEURL}/1r8e32mi8hrxadj/cmark-0.28.3-1-src.tar.xz
wget ${BASEURL}/qoi79xunuvyinjt/cmark-0.28.3-1.hint
wget ${BASEURL}/r0ssovzt1m4dr0i/cmark-0.28.3-1.tar.xz
mkdir cmark-debuginfo cmark-devel libcmark0_28_3
cd cmark-debuginfo
wget ${BASEURL}/synv3v6lk9okaui/cmark-debuginfo-0.28.3-1.hint
wget ${BASEURL}/3koao7t6zw966f9/cmark-debuginfo-0.28.3-1.tar.xz
cd ../cmark-devel
wget ${BASEURL}/wlpk33vdn6ht9z0/cmark-devel-0.28.3-1.hint
wget ${BASEURL}/ny68t30s10np2t6/cmark-devel-0.28.3-1.tar.xz
cd ../libcmark0_28_3
wget ${BASEURL}/b7fs8exm6jciy8p/libcmark0_28_3-0.28.3-1.hint
wget ${BASEURL}/mns1r31qibshuvv/libcmark0_28_3-0.28.3-1.tar.xz
popd
next reply other threads:[~2018-01-21 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 23:31 David Stacey [this message]
2018-01-28 14:58 ` Jon Turney
2018-01-28 19:35 ` David Stacey
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=dcd1a708-511e-cf6a-088f-51e1bb81a715@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).