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: Tue, 25 Apr 2023 23:13:18 +0100 [thread overview]
Message-ID: <4c07f04c-6416-c10e-0677-ec0360c2efd7@dronecode.org.uk> (raw)
In-Reply-To: <CAA3frXR9dsu18KNi2vCxM3Yofab-JkdTKSF54=9hd6ZFLVuSQQ@mail.gmail.com>
On 25/04/2023 22:10, Daisuke Fujimura via Cygwin-apps wrote:
> Thank you for your response.
>
> Following the announcement of the previous update, I would like to
> note that the binaries need to be recompiled.
> - https://www.mail-archive.com/cygwin-announce-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org/msg08753.html
Yeah, I'm not quite sure what that statement means. It's not literally
"every single binary in cygwin"
I don't really know enough about ruby be sure how to interpret it.
There's some subset of packages which need rebuilding (as discussed
below), and maybe any locally installed gems which have binaries?
>> I applied my usual workaround (which is adding 'ruby_23' to an internal
>> list of things which are allowed to not be provided), and set the job to
>> rerun, which seems to have succeeded.
>
> Does this mean adding `ruby_23` to `depend2` in some packages in setup.ini?
Not really.
The failure was a consequence of that. As previously mentioned, using
some special tools, I've retroactively added appropriate ruby_xy
requires: in the .hint files for existing packages which:
* install into /usr/lib/ruby/vendor_ruby/x.y/
* install into /usr/lib/gems/ruby/x.y/
* contain executable files linked to cygrubyxy0.dll because they embed a
ruby interpreter (which seems to be just kross-ruby, kf5-kross-ruby and
weechat-ruby)
> I would like to know more about the specifications of setup.ini. Is
> there any documentation available somewhere?
Sure, the documentation is at:
https://sourceware.org/cygwin-apps/setup.ini.html
Feel free to ask if you have further questions not covered by that.
next prev parent reply other threads:[~2023-04-25 22:13 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
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 [this message]
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=4c07f04c-6416-c10e-0677-ec0360c2efd7@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).