From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: New cygport: perl-WWW-Curl
Date: Mon, 30 Mar 2015 19:15:00 -0000 [thread overview]
Message-ID: <87384me3qe.fsf@Rainer.invalid> (raw)
In-Reply-To: <1427740114.8576.35.camel@cygwin.com> (Yaakov Selkowitz's message of "Mon, 30 Mar 2015 13:28:34 -0500")
Yaakov Selkowitz writes:
>> Producing a cygport file for a Perl distribution is not a problem. The
>> question here is how stable the libcurl API is, since that determines if
>> the package should be updated by the curl maintainer or somebody else
>> (me, most likely).
>
> The libcurl API is quite stable.
OK, I'll prepare an ITP.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-03-30 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 17:14 Florian Friesdorf
2015-03-30 18:28 ` Achim Gratz
2015-03-30 18:32 ` Yaakov Selkowitz
2015-03-30 19:15 ` Achim Gratz [this message]
2015-04-06 19:09 ` Florian Friesdorf
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=87384me3qe.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@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).