public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Question regarding OpenSSL 1.1.1b package configuration against OpenSSL 1.0.2r
Date: Tue, 04 Jun 2019 15:25:00 -0000	[thread overview]
Message-ID: <51f3bec1-cd1e-cda9-31ed-174b09c763f6@SystematicSw.ab.ca> (raw)
In-Reply-To: <5cf5a0f7.1c69fb81.cfbf0.b1e6@mx.google.com>

On 2019-06-03 16:36, Steven Penny wrote:
> On Mon, 3 Jun 2019 14:35:29, Brian Inglis wrote:
>> You can easily rebuild the package yourself with the cygport utility, to check
>> that works, then change the build config to include the Brainpool ECs, and
>> rebuild the way you want it.
> 
> Please do not presume someones technical prowess. It might be easy *to you*, but
> its certainly not easy in an objective sense, and definitely not to a novice
> Cygwin user.
> 
> This is coming from someone who has built hundreds of Cygwin and Mingw64
> packages. Have some perspective.

I am encouraging and offering the poster a way to solve their problem, after
providing some possible reasons for dropping support from some ECs.
Rebuilding a Cygwin package from source using cygport is a relatively easy task.
I am not presuming, but assuming some amount of technical expertise, based on a
poster asking about openssl configuration and which ECs they want to support.
If they need more help they can ask in a follow up.

Please refrain from your own inappropriate assumptions and meta-commentary based
on that, as this is not a social media platform.
Why would you assume the poster is a novice?
Before commenting, please try yourself to consider multiple perspectives on
posts and replies?
"There are more things in heaven and Earth, Horatio, Than are dreamt of in your
philosophy." Hamlet: Shakespeare

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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

  parent reply	other threads:[~2019-06-04 15:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 12:09 Benjamin Baratte
2019-06-03 20:35 ` Brian Inglis
2019-06-03 22:36   ` Steven Penny
2019-06-04 14:32     ` Benjamin Baratte
2019-06-04 15:25     ` Brian Inglis [this message]
2019-06-04 22:56       ` Steven Penny
2019-06-05  3:04         ` Vince Rice
2019-06-05  4:12           ` Steven Penny
2019-06-05  4:26           ` Houder
2019-06-05  6:24             ` Brian Inglis

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=51f3bec1-cd1e-cda9-31ed-174b09c763f6@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).