From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: William Hubbs <williamh@gentoo.org>
Subject: Re: [gentoo-dev] the state of dev-lang/lua
Date: Sun, 24 Mar 2019 14:26:35 +0100 [thread overview]
Message-ID: <4861005.cn4WkK61Ef@pinacolada> (raw)
In-Reply-To: <20190323212327.GA24656@linux1.home>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
Am Samstag, 23. März 2019, 22:23:27 CET schrieb William Hubbs:
> Hi all,
>
> Soon I will be working on fixing up the state of dev-lang/lua, and there
> are a couple of things I want to mention.
>
> The first thing is liblua as a shared library. If you are using lua
> internally in a program, upstream strongly recommends not linking it
> this way; it is supposed to be statically linked into the executable.
> Because of this, and because of the amount of custom patching we do to
> maintain liblua as a shared library, I plan to stop creating the shared
> library.
>
Please dont. Static linking is a security nightmare.
I'd much rather consider removing the static library, and fix programs broken
by that. (No matter what silly opinions lua upstream has.)
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2019-03-24 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 21:23 [gentoo-dev] the state of dev-lang/lua William Hubbs
2019-03-24 4:28 ` Michał Górny
2019-03-24 11:24 ` contact
2019-03-24 18:46 ` William Hubbs
2019-03-24 13:26 ` Andreas K. Huettel [this message]
2019-03-24 17:44 ` William Hubbs
2019-03-24 18:47 ` Michał Górny
2019-03-25 4:23 ` Robin H. Johnson
2019-03-25 6:16 ` Michał Górny
2019-03-26 21:30 ` Patrick McLean
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=4861005.cn4WkK61Ef@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=williamh@gentoo.org \
/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