public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: curl calm issue
Date: Tue, 01 Dec 2020 07:02:18 +0100	[thread overview]
Message-ID: <87sg8qukr9.fsf@Otto.invalid> (raw)
In-Reply-To: <71b97bcc-62dc-c79b-f987-5464cfd99775@SystematicSw.ab.ca> (Brian Inglis's message of "Mon, 30 Nov 2020 18:06:16 -0700")

Brian Inglis writes:
> The issue is that previous releases were always generated with
> debuginfo, but the latest release also changes debug behaviour to
> strictly check SSL protocol, causing execution issues with users and
> downstreams.

I read upstreams response that this will become the default behaviour
anyway, so I'd not spend any effort on working around this issue unless
you are fairly certain that youi can convince them otherwise.

> I would like to generate the updated release without the behaviour
> change and that appears to also eliminate debuginfo generation.

Then you need to patch out the corrsponding change.  I have not looked
if they lumped it into another define (which would be more difficult) or
if just the configury does an extra define for this error checking (just
undefine it).

> If I need to generate release -2 without debuginfo, how do I avoid
> this issue?

Again, don't.

> Alternatively, could I use separate cygport files to generate the lib
> and bin subpackages without debuginfo, and the devel package with
> debuginfo and the strict SSL protocol check, and how would that work
> with calm?

Please not and no, that sort of nonsense isn't supported by setup anyway.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

  reply	other threads:[~2020-12-01  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <160678137911.641109.8028997546055063113@server2.sourceware.org>
2020-12-01  1:06 ` Brian Inglis
2020-12-01  6:02   ` ASSI [this message]
2020-12-01 15:34   ` Jon Turney
2020-12-01 16:26     ` 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=87sg8qukr9.fsf@Otto.invalid \
    --to=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).