From: Jon Turney <jon.turney@dronecode.org.uk>
To: Daisuke Fujimura <booleanlabel@gmail.com>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITA] ruby 3.2.2
Date: Mon, 24 Apr 2023 21:10:56 +0100 [thread overview]
Message-ID: <01697347-7b78-e3e9-6056-0e92e0cb994a@dronecode.org.uk> (raw)
In-Reply-To: <CAA3frXTfDpTod5AQtVHtTwH58rZWk91Sfi8pa8zhJt8je9S2bw@mail.gmail.com>
On 24/04/2023 00:44, Daisuke Fujimura via Cygwin-apps wrote:
>> This is what I get for not trying these things. I think nesting the
>> substitution like that isn't valid in bash, so maybe:
>>
>> SOVERSION=${VERSION%.*}
>> ruby_PROVIDES="ruby_${SOVERSION//./}"
>>
>> actually works?
>
> It worked. Thank you very much.
>
> ```
> $ cygport ruby.cygport vars ruby_PROVIDES
> declare -- ruby_PROVIDES="ruby_32"
> ```
>
> - https://cygwin.com/cgit/cygwin-packages/playground/commit/?id=9b448625c2166d5c7310c295bfa4328d24ac5444
> - https://github.com/cygwin/scallywag/actions/runs/4780609520/jobs/8498537391
>
>
> I think I can release ruby-3.2.2-1 without applying the cygport patch,
> but is there any problem if I deploy it?
I don't think so. Please, go ahead and deploy.
> (The cygport patch should not be needed until someone rebuilds the
> ruby-* subpackages.)
Right. Hopefully I'll get around around to doing a cygport release with
that change this week.
next prev parent reply other threads:[~2023-04-24 20:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 22:42 Daisuke Fujimura
2023-04-20 3:28 ` Marco Atzeri
2023-04-20 10:50 ` Jon Turney
2023-04-20 16:13 ` Jon Turney
2023-04-21 19:36 ` Daisuke Fujimura
2023-04-21 20:06 ` Jon Turney
2023-04-22 12:04 ` Daisuke Fujimura
2023-04-23 13:35 ` Jon Turney
2023-04-23 23:44 ` Daisuke Fujimura
2023-04-24 20:10 ` Jon Turney [this message]
2023-04-25 9:56 ` Daisuke Fujimura
2023-04-25 13:52 ` Jon Turney
2023-04-25 21:10 ` Daisuke Fujimura
2023-04-25 22:13 ` Jon Turney
2023-04-25 22:37 ` Daisuke Fujimura
2023-06-08 14:38 ` [GOLDSTAR] " Jon Turney
2023-06-13 15:04 ` Andrew Schulman
2023-06-13 23:24 ` Daisuke Fujimura
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=01697347-7b78-e3e9-6056-0e92e0cb994a@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=booleanlabel@gmail.com \
--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).