From: Stephen John Smoogen <smooge@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: openssl-1.0.2g-3
Date: Thu, 10 Mar 2016 01:07:00 -0000 [thread overview]
Message-ID: <CANnLRdjWxM-Ki0wOa2TeBp7YRrzi-cZoSa=0oiQSZ-D4bdj3+w@mail.gmail.com> (raw)
In-Reply-To: <CACoZoo3Lho3quaj7YDNB1WzK3matGsZSG_v70RAY6qDSq90AqA@mail.gmail.com>
On 9 March 2016 at 15:53, Erik Soderquist <ErikSoderquist@gmail.com> wrote:
> On Wed, Mar 9, 2016 at 5:18 PM, Corinna Vinschen wrote:
>> On Mar 9 16:54, Erik Soderquist wrote:
> <snip>
>>> If I knew how, I would...
>>
>> https://cygwin.com/setup.html
>>
>> A couple of months ago I made sure that portable LibreSSL from
>> https://github.com/libressl-portable/portable.git at least doesn't
>> forget to support Cygwin, should we ever intend to switch. I don't
>> expect any (serious) bit-rot so far.
>
> I meant that I'm not a programmer at all; I've only written scripts
> before, and am just barely started studying my first programming
> language.
>
> If actually knowing the language isn't needed, I can certainly try,
> but if knowing the language the package is written in is required, I'm
> currently woefully under qualified to take up the mantle
>
It isn't really usable unless you are a programmer because it isn't a
fall in replacement for openssl. [It may work but mostly needs
recompiles and a lot of programming fixes to get it to work with other
things.] I would say that if you aren't in that camp.. you don't
really need it at the moment.
> -- Erik
>
> --
> 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
>
--
Stephen J Smoogen.
--
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
prev parent reply other threads:[~2016-03-10 1:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 12:55 Corinna Vinschen
2016-03-08 17:03 ` Ismail Donmez
2016-03-08 17:47 ` Corinna Vinschen
2016-03-09 16:21 ` Erik Soderquist
2016-03-09 21:50 ` Andrey Repin
2016-03-09 21:54 ` Erik Soderquist
2016-03-09 22:19 ` Corinna Vinschen
2016-03-09 22:53 ` Erik Soderquist
2016-03-10 1:07 ` Stephen John Smoogen [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='CANnLRdjWxM-Ki0wOa2TeBp7YRrzi-cZoSa=0oiQSZ-D4bdj3+w@mail.gmail.com' \
--to=smooge@gmail.com \
--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).