public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Ken Brown <kbrown@cornell.edu>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [Attn. MAINTAINERS] Heads up: Perl 5.36.1 is imminent
Date: Tue, 9 May 2023 21:15:35 +0100	[thread overview]
Message-ID: <230a85ba-4a64-9b8f-b0d2-e19588a887e9@dronecode.org.uk> (raw)
In-Reply-To: <94093430-c37c-cca3-2c51-b6e679d03cf8@cornell.edu>

On 06/05/2023 19:31, Ken Brown via Cygwin-apps wrote:
> On 5/6/2023 9:34 AM, Jon Turney wrote:
>> (There's definitely a problematic dependency chain cygport -> automake 
>> -> automake1.* -> texinfo -> versioned perl which we need to be aware 
>> of in future when rebuilding texinfo for updated perl)
> 
> In addition to the dependencies above, there's actually a direct 
> dependency cygport -> texinfo.

Doh, right!

> I was aware of this when rebuilding texinfo, after an initial failed 
> attempt using SCALLYWAG.  The way I dealt with it was to forcibly update 
> perl, ignoring setup's warnings.  I don't know if there's a better way 
> to handle this in the future.  Maybe temporarily (or permanently?) 
> remove those dependencies on texinfo?

I think perhaps that maybe making those dependencies of cygport 
'suggests'/'recommended' (if we implemented that) rather than 'depends', 
as that would let the solver consider solutions without those packages 
installed.

I think would be ok, as texinfo doesn't actually require itself to build?

(There are perhaps a few packages which do have a real self-build-dep, 
but those are probably harder to build anyhow, and it should be 
explicitly recorded in build-requires?)


  reply	other threads:[~2023-05-09 20:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 20:00 Achim Gratz
2023-05-01 20:28 ` Marco Atzeri
2023-05-02  6:36   ` ASSI
2023-05-02 19:47 ` Achim Gratz
2023-05-05 20:15   ` Marco Atzeri
2023-05-05 20:44     ` Jon Turney
     [not found]       ` <43354da8-65cc-7224-fcee-81fe38afb512@gmail.com>
2023-05-06 13:12         ` Jon Turney
2023-05-07 11:39           ` Marco Atzeri
2023-05-02 20:34 ` Jon Turney
2023-05-02 20:45   ` Achim Gratz
2023-05-03 12:19     ` Ken Brown
2023-05-03 13:33       ` Jon Turney
2023-05-03 14:47         ` Ken Brown
2023-05-03 16:51           ` Achim Gratz
2023-05-03 18:41             ` Achim Gratz
2023-05-03 16:55         ` Achim Gratz
2023-05-03 22:01       ` Ken Brown
2023-05-06 13:34         ` Jon Turney
2023-05-06 18:31           ` Ken Brown
2023-05-09 20:15             ` Jon Turney [this message]
2023-05-20  7:57   ` Achim Gratz
2023-10-23 18:53   ` Jon Turney
2023-12-15 17:15     ` Jon Turney
2024-01-28 16:40       ` Jon Turney

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=230a85ba-4a64-9b8f-b0d2-e19588a887e9@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=kbrown@cornell.edu \
    /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).