From: Maxime Devos <maximedevos@telenet.be>
To: Remco van 't Veer <remco@remworks.net>, 56322@debbugs.gnu.org
Subject: bug#56322: Ruby packaging issues
Date: Wed, 24 Aug 2022 20:41:14 +0200 [thread overview]
Message-ID: <633700ec-bdf9-1ed6-d6ae-ce8587c6b245@telenet.be> (raw)
In-Reply-To: <87o7w9ll4x.fsf@jomco.nl>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 658 bytes --]
On 24-08-2022 17:24, Remco van 't Veer wrote:
>> * Ruby contains some things generated by bison or such.
> It seems the generated parse.c file (from parse.y) is included in the
> tarballs as a service to workaround a bootstrap problem; generating the
> parser requires ruby. See also:
>
> https://github.com/ruby/ruby/blob/master/common.mk#L910
See my other reply, and also:
Even if generating the .c from the .y from the Ruby code would be ideal,
at least generating the .c from the .y (and using the pre-generated the
.y) is still an improvement, it would at least help with the 'buggy
bison' scenario.
Greetings,
Maxime.
[-- Attachment #1.1.1.2: Type: text/html, Size: 1295 bytes --]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-08-24 18:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 11:15 bug#56322: Ruby packaging issues Maxime Devos
2022-08-24 15:24 ` Remco van 't Veer
2022-08-24 18:38 ` Maxime Devos
2022-08-25 10:44 ` Remco van 't Veer
2022-08-24 18:41 ` Maxime Devos [this message]
2022-08-24 15:27 ` bug#56322: [PATCH 0/2] " Remco van 't Veer
2022-08-24 15:27 ` bug#56322: [PATCH 1/2] gnu: ruby: trigger autotools bootstrap Remco van 't Veer
2022-08-24 15:27 ` bug#56322: [PATCH 2/2] gnu: ruby: fix unbundling of libffi for inheriting rubies Remco van 't Veer
2022-08-25 10:45 ` bug#56322: [PATCH] gnu: ruby: regenerate parse.c Remco van 't Veer
2022-10-08 10:01 ` bug#56322: Debbug 56322, Ruby packaging issues, ping? Remco van 't Veer
2022-10-09 9:15 ` Maxime Devos
2022-10-10 5:05 ` Remco van 't Veer
2022-10-10 10:27 ` Maxime Devos
2022-10-12 13:35 ` bug#56322: [PATCH core-updates 0/3] Ruby packaging issues Remco van 't Veer
2022-10-12 13:35 ` bug#56322: [PATCH core-updates 1/3] gnu: ruby: trigger autotools bootstrap Remco van 't Veer
2022-10-12 13:35 ` bug#56322: [PATCH core-updates 2/3] gnu: ruby: fix unbundling of libffi for inheriting rubies Remco van 't Veer
2022-10-12 13:35 ` bug#56322: [PATCH core-updates 3/3] gnu: ruby: regenerate parse.c Remco van 't Veer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=633700ec-bdf9-1ed6-d6ae-ce8587c6b245@telenet.be \
--to=maximedevos@telenet.be \
--cc=56322@debbugs.gnu.org \
--cc=remco@remworks.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).