From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Baines <mail@cbaines.net>
Cc: 28773@debbugs.gnu.org
Subject: [bug#28773] [PATCH] Wrap bin files in the ruby build system.
Date: Mon, 16 Oct 2017 15:19:09 +0200 [thread overview]
Message-ID: <877evvdycy.fsf@gnu.org> (raw)
In-Reply-To: <20171010084452.036b3052@cbaines.net> (Christopher Baines's message of "Tue, 10 Oct 2017 08:44:52 +0100")
Hi Chris,
Christopher Baines <mail@cbaines.net> skribis:
> This is a bit experimental. There is some description of the motivation
> behind this approach, as well as the downsides in the commit messages.
>
> I don't know how to wrap binaries with the GEM_PATH, but somehow
> excluding inputs specified as native-inputs, so I'd be very interested
> if anyone has ideas about this.
>
> Christopher Baines (3):
> ruby-build-system: Add wrap-ruby-program.
> ruby-build-system: Add a new wrap phase.
> gnu: Remove redundant wrapping from packages using ruby-build-system.
Cc’ing Ben who is another Serious Ruby User I think. :-)
Ludo’.
next prev parent reply other threads:[~2017-10-16 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 7:44 [bug#28773] [PATCH] Wrap bin files in the ruby build system Christopher Baines
2017-10-10 7:47 ` [bug#28773] [PATCH 1/3] ruby-build-system: Add wrap-ruby-program Christopher Baines
2017-10-10 7:47 ` [bug#28773] [PATCH 2/3] ruby-build-system: Add a new wrap phase Christopher Baines
2017-10-10 7:47 ` [bug#28773] [PATCH 3/3] gnu: Remove redundant wrapping from packages using ruby-build-system Christopher Baines
2017-10-16 13:19 ` Ludovic Courtès [this message]
2017-10-18 10:39 ` [bug#28773] [PATCH] Wrap bin files in the ruby build system Ben Woodcroft
2018-01-11 21:47 ` Ludovic Courtès
2018-01-12 6:51 ` Ben Woodcroft
2018-01-14 22:22 ` Christopher Baines
2018-01-14 22:22 ` Christopher Baines
2018-01-14 22:25 ` bug#28773: [PATCH] Specify native search path for all ruby packages Christopher Baines
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=877evvdycy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28773@debbugs.gnu.org \
--cc=mail@cbaines.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.