public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: gs-cygwin.com@gluelogic.com
To: Achim Gratz <Stromeko@nexgo.de>
Cc: cygwin-apps@cygwin.com
Subject: Re: [ITA] openssl, openssl10, mingw64-{i686,x86_64}-openssl
Date: Sun, 28 Nov 2021 05:09:43 -0500	[thread overview]
Message-ID: <YaNVZ+Bmwn8iwahu@xps13> (raw)
In-Reply-To: <87a6ho642c.fsf@Rainer.invalid>

On Sun, Nov 28, 2021 at 10:07:55AM +0100, Achim Gratz wrote:
> 
> [...]
> For the MinGW64 packages the current plan (based on the previous
> discussion) is to update them with the 1.0.2 version and provide the
> 1.1.1 version (without renaming the packages or introducing any new
> package names) as a test version only.  This means that the existing
> packages depending on mingw64-{i686,x86_64}-openssl will still work
> correctly, but can be rebuilt using the 1.1.1 version by chosing the
> test version (whatever the likelyhood of that actually happening is).

FWIW, I have been using the cygwin-provided MinGW64 environment for
porting lighttpd to native Windows.  It is the only working environment
I found where I did not have to bootstrap everything from scratch.

If one does not want to build everything statically and does not want
to build one's own distro-like package management on top of Windows,
one finds themselves SoL on Windows if one thinks Microsoft cares.
Developing on Microsoft platforms is an awful experience for anything
beyond a trivial app.

Achim, thank you for your efforts on MinGW64 packages.

Cheers, Glenn

      parent reply	other threads:[~2021-11-28 10:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28  9:07 Achim Gratz
2021-11-28  9:22 ` Marco Atzeri
2021-11-28  9:43   ` ASSI
2021-11-28 10:52     ` Marco Atzeri
2021-11-28 12:28       ` Achim Gratz
2021-11-28 10:09 ` gs-cygwin.com [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=YaNVZ+Bmwn8iwahu@xps13 \
    --to=gs-cygwin.com@gluelogic.com \
    --cc=Stromeko@nexgo.de \
    --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).