From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
Cc: 38500@debbugs.gnu.org, Brett Gilio <brettg@posteo.net>,
Vicente Eduardo <vic798@gmail.com>
Subject: bug#38500: Ruby is built against libruby-static.a
Date: Sun, 08 Dec 2019 16:42:15 +0100 [thread overview]
Message-ID: <87a782bz90.fsf@nckx> (raw)
In-Reply-To: <87fthwdr0p.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Vincente, Brett,
Brett Gilio 写道:
> Vicente Eduardo <vic798@gmail.com> writes:
>
>> I would like to have two versions, or at least the dynamic one,
>> that's the common way
>> Ruby should be built, and also the Guixy style.
Important: static linking isn't the Guixy style at all!
Statically linking different packages ‘subverts’ Guix, can subvert
grafting and lead to undetected security holes.
> Generally, I think we dynamically link most objects.
Correct.
> _BUT_, I could be
> missing part of the story here. So I am going to wait for the
> higher
> powers that be to respond.
You could ask Pjotr Prins and David Thompson but I suspect that it
was simply an oversight: most packages link dynamically by default
because it's the sane thing to do, and it would have been
reasonable to assume Ruby did too.
If there is a good reason to link statically, it should be added
in a comment.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-12-08 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 13:25 bug#38500: Ruby is built against libruby-static.a Vicente Eduardo
2019-12-07 16:44 ` Brett Gilio
2019-12-08 14:44 ` Vicente Eduardo
2019-12-08 14:49 ` Vicente Eduardo
2019-12-08 15:42 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2019-12-09 18:33 ` Brett Gilio
2019-12-09 20:57 ` Brett Gilio
2019-12-13 3:51 ` Brett Gilio
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=87a782bz90.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=38500@debbugs.gnu.org \
--cc=brettg@posteo.net \
--cc=me@tobias.gr \
--cc=vic798@gmail.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.
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.