public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: OpenSSL package updates
Date: Sun, 7 Nov 2021 11:39:14 +0000	[thread overview]
Message-ID: <248aae90-baa9-4115-2a05-b527e8480686@dronecode.org.uk> (raw)
In-Reply-To: <87ee7smhaw.fsf@Rainer.invalid>

On 07/11/2021 09:44, Achim Gratz wrote:
> Corinna Vinschen via Cygwin-apps writes:
> 
> I have no problem with that idea as long as the previous packages can be
> reinstated for inspection if necessary.
> 
>> In a second step the dependencies in the below packages could be changed
>> to require the mingw-libopenssl100 package.  At least that would be
>> better for bookkeeping.  Does that require manual intervention on the
>> server?  I'm not sure, Jon would know this better.
> 
> Yes, all the hint files would need to get edited.

Stop!

We don't put the soversion into cross-package names.

I don't think we are the only distro to do that.

I don't think it makes any sense to do so, as there's no executables in 
other cross-packages which use that shared library.

Any user cross-built executables will need to be rebuilt after this 
update (and the names of any shared libraries distributed with the 
cross-built executable updated)

I get that this is trying to avoid having to rebuild all the dependent 
cross-packages right now, but they need to be rebuilt eventually, and 
making stuff more complex just for that temporarily state doesn't seem 
useful.

      reply	other threads:[~2021-11-07 11:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24 15:25 Achim Gratz
2021-11-06 15:58 ` Achim Gratz
2021-11-06 17:24   ` Corinna Vinschen
2021-11-06 19:59     ` Achim Gratz
2021-11-06 21:17       ` Corinna Vinschen
2021-11-07  9:44         ` Achim Gratz
2021-11-07 11:39           ` Jon Turney [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=248aae90-baa9-4115-2a05-b527e8480686@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).