public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] the state of dev-lang/lua
Date: Mon, 25 Mar 2019 07:16:20 +0100	[thread overview]
Message-ID: <dd70a148fcaba22b94028d0864ea8ecd7ab24659.camel@gentoo.org> (raw)
In-Reply-To: <robbat2-20190325T032311-646182547Z@orbis-terrarum.net>

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

On Mon, 2019-03-25 at 04:23 +0000, Robin H. Johnson wrote:
> > Are there more packages in the tree that are locked to a specific version of lua?
> Yes, several, and more on that in a second.
> 
> I think packages will need one of two variables:
> LUA_SINGLE_TARGET
> LUA_TARGETS
> 
> LUA_TARGETS is probably only going to be used by the dev-lua/ modules.
> LUA_SINGLE_TARGET is probably going to be used by MOST packages that
> include Lua as an embedded scripting language; of which I'll discuss a
> few below.
> 

Please don't copy the PYTHON_* insanity here.  The only reason for
PYTHON_SINGLE_TARGET, as I keep repeating, is that we *needed* a sane
default of py2+py3 for a lot of packages, without causing REQUIRED_USE
violations all over the place.

I don't think Lua situation is similar.  That is, I don't think you can
pinpoint a combination of 2 or more default 'targets' and a single
'target' that would work for the majority of packages.  Just use
a single USE_EXPAND combined with REQUIRED_USE and sane defaults.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

  reply	other threads:[~2019-03-25  6:16 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
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 [this message]
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=dd70a148fcaba22b94028d0864ea8ecd7ab24659.camel@gentoo.org \
    --to=mgorny@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