From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: lua upgrade plan
Date: Mon, 3 Jul 2017 06:32:49 +0300 [thread overview]
Message-ID: <20170703063249.532b2819803bb2516b2b25a1@gentoo.org> (raw)
In-Reply-To: <20170702153012.GA32505@linux1.home>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Hi,
On Sun, 2 Jul 2017 10:30:12 -0500 William Hubbs wrote:
> > All that said, in FLOSS, he who volunteers, makes the rules, and
> > particularly given the upstream opposition meaning more gentoo-level work
> > required, if there's nobody willing to support lua in gentoo with dynamic
> > linking...
>
> You are correct. Basically we have to write our own build system and
> keep it up to date for every version of lua in order to support this.
Why should we? We can borrow from other distributions like Debian
or Fedora. Of course some Gentoo-specific tuning may be required,
but it will be not writing from scratch.
> If someone can convince upstream to support it, this would be far better for
> everyone.
In the ideal world, yes, I agree with this. But we are in real
world with real lua developers unwilling to cooperate from what I
see.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-03 3:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 17:16 [gentoo-dev] lua upgrade plan William Hubbs
2017-07-01 8:16 ` Azamat Hackimov
2017-07-01 12:18 ` Vadim A. Misbakh-Soloviov
2017-07-01 16:53 ` William Hubbs
2017-07-02 3:55 ` [gentoo-dev] " Duncan
2017-07-02 15:30 ` William Hubbs
2017-07-03 1:43 ` Duncan
2017-07-03 3:32 ` Andrew Savchenko [this message]
2017-07-03 12:08 ` Martin Vaeth
2017-07-02 20:12 ` [gentoo-dev] " Vadim A. Misbakh-Soloviov
2017-07-02 20:14 ` M. J. Everitt
2017-07-03 14:41 ` William Hubbs
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=20170703063249.532b2819803bb2516b2b25a1@gentoo.org \
--to=bircoph@gentoo.org \
--cc=gentoo-dev@lists.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