From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFU] poco-1.4.6p2-1
Date: Wed, 09 Oct 2013 19:47:00 -0000 [thread overview]
Message-ID: <5255B2D7.4060905@gmail.com> (raw)
In-Reply-To: <52409188.2090902@tiscali.co.uk>
Il 9/23/2013 9:07 PM, David Stacey ha scritto:
> # 32-bit:
> BASEURL=https://dl.dropboxusercontent.com/u/119453582/Cygwin/32bit/release
> wget --no-check-certificate --no-host-directories --force-directories
> --cut-dirs=5 \
> ${BASEURL}/poco/libpoco-devel/libpoco-devel-1.4.6p2-1.tar.xz \
> ${BASEURL}/poco/libpoco-devel/setup.hint \
> ${BASEURL}/poco/libpoco-doc/libpoco-doc-1.4.6p2-1.tar.xz \
> ${BASEURL}/poco/libpoco-doc/setup.hint \
> ${BASEURL}/poco/libpoco16/libpoco16-1.4.6p2-1.tar.xz \
> ${BASEURL}/poco/libpoco16/setup.hint \
> ${BASEURL}/poco/poco-1.4.6p2-1-src.tar.xz \
> ${BASEURL}/poco/poco-1.4.6p2-1.tar.xz \
> ${BASEURL}/poco/poco-debuginfo/poco-debuginfo-1.4.6p2-1.tar.xz \
> ${BASEURL}/poco/poco-debuginfo/setup.hint \
> ${BASEURL}/poco/setup.hint
>
>
> # 64-bit:
> BASEURL=https://dl.dropboxusercontent.com/u/119453582/Cygwin/64bit/release
> wget --no-check-certificate --no-host-directories --force-directories
> --cut-dirs=5 \
> ${BASEURL}/poco/libpoco-devel/libpoco-devel-1.4.6p2-1.tar.xz \
> ${BASEURL}/poco/libpoco-devel/setup.hint \
> ${BASEURL}/poco/libpoco-doc/libpoco-doc-1.4.6p2-1.tar.xz \
> ${BASEURL}/poco/libpoco-doc/setup.hint \
> ${BASEURL}/poco/libpoco16/libpoco16-1.4.6p2-1.tar.xz \
> ${BASEURL}/poco/libpoco16/setup.hint \
> ${BASEURL}/poco/poco-1.4.6p2-1-src.tar.xz \
> ${BASEURL}/poco/poco-1.4.6p2-1.tar.xz \
> ${BASEURL}/poco/poco-debuginfo/poco-debuginfo-1.4.6p2-1.tar.xz \
> ${BASEURL}/poco/poco-debuginfo/setup.hint \
> ${BASEURL}/poco/setup.hint
>
>
> Please leave 1.4.6p1-1 as previous.
>
> Many thanks in advance for uploading,
>
> Dave.
>
done
prev parent reply other threads:[~2013-10-09 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 19:07 David Stacey
2013-10-09 19:47 ` marco atzeri [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=5255B2D7.4060905@gmail.com \
--to=marco.atzeri@gmail.com \
--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).