public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Azamat Hackimov <azamat.hackimov@gmail.com>
To: gentoo-dev@lists.gentoo.org, rafaelmartins@gentoo.org
Subject: Re: [gentoo-dev] lua upgrade plan
Date: Sat, 1 Jul 2017 13:16:02 +0500	[thread overview]
Message-ID: <CAFqVybqM2LoJ9PpqsR_bYRsmqn5jfpO9qqafHDvX5peAd4miGg@mail.gmail.com> (raw)
In-Reply-To: <20170630171606.GA7044@whubbs1.gaikai.biz>

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

2017-06-30 22:16 GMT+05:00 William Hubbs <williamh@gentoo.org>:

> All,
>
> Upstream does not support liblua as a shared library, and they do not
> support installing multiple versions of lua onto a system. After
> conferring with the other lua maintainer, the decision has been made to
> remove this custom support from our lua package as well. This has been
> talked about many times upstream.


Lua devs very "hostile" to Linux distributers. I don't see why we should do
as they want to do.
They not have open vcs to simply see what they changes in new release, they
don't accepts
patches for system integration. They didn't even elementary easy-to-use
build system. Just
look to another distributives, they all do versioned and shared libraries
of Lua 5.{1,2,3}. Fedora
devs did custom Autotools-based buildsystem, Debian - provided pkg-config
files. There also
exists excellent LuaDist framework - still outdated, yes, but we can take
from them CMake
buildsystem to provide better integration into Gentoo enviroment. You have
so many options
but you still want to follow unwelcome Lua rules.


> They do not want it, and using liblua as a shared library causes
> performance issues.
>

Why, we live in XXI century, where this argument came from? What about
security, did you
forgot about it? How do you planning to do backward compatibility with old
lua5.1 libraries
and projects? They definitely have breakage since lua 5.2 and 5.3 not
compatible with each
other. Why Lua can't have same eclass as multislotted Python or Ruby? Lua
ecosystem not
so big, about 500 packages so why there no even little efforts to make Lua
support in Gentoo
better?

-- 
From Siberia with Love!

[-- Attachment #2: Type: text/html, Size: 2421 bytes --]

  reply	other threads:[~2017-07-01  8:16 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 [this message]
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
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=CAFqVybqM2LoJ9PpqsR_bYRsmqn5jfpO9qqafHDvX5peAd4miGg@mail.gmail.com \
    --to=azamat.hackimov@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=rafaelmartins@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