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

On Tue, 4 Jun 2019 09:25:48, Brian Inglis wrote:
> 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.

Easy compared to what, assembly? I am comfortable with 3 programming languages,
and learning 4 others, and compiling C is not "relatively easy". Especially
considering the scope:

    $ cd openssl-master
    $ find -name '*.c' -exec wc -l {} + | tail -1
    419738 total

400,000 lines of C.

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

reread the post:

https://cygwin.com/ml/cygwin/2019-06/msg00012.html

He shows some domain knowledge of OpenSSL, but where are you getting that he
knows about compiling C? A conservative read would reveal that he might have no
knowledge of compiling C, and you want him to compile 400,000 lines of C because
its "easy".

> Please refrain from your own inappropriate assumptions and meta-commentary
> based on that, as this is not a social media platform.

No, but it is a public forum. and I will call out nonsense if I see it. As your
type of comments are off putting to new users.

> Why would you assume the poster is a novice? Before commenting, please try
> yourself to consider multiple perspectives on posts and replies?

As should you.


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

  reply	other threads:[~2019-06-04 22:56 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
2019-06-04 22:56       ` Steven Penny [this message]
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=5cf6f6fe.1c69fb81.9ba14.25bc@mx.google.com \
    --to=svnpenn@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).