public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marek Szuba <marecki@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/2] eclass: Add first version of lua.eclass
Date: Fri, 4 Sep 2020 10:38:17 +0200	[thread overview]
Message-ID: <a84cace2-33f1-7d25-687f-a9a503644e1f@gentoo.org> (raw)
In-Reply-To: <20200903133707.106176-2-marecki@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1535 bytes --]

On 2020-09-03 15:37, Marek Szuba wrote:

For the record, some mostly-cosmetic issues that have already been
identified. Will include them in the next revision:

> +if [[ ! ${_LUA_R0} ]]; then
> +
> +inherit multibuild toolchain-funcs
> +
> +BDEPEND="virtual/pkgconfig"

There should be no BDEPEND in the eclass any more, it's a leftover from
an earlier iteration which retrieved module directories in less
conditional fashion.

> +# Please note that you can also use bash brace expansion if you like:
> +# @CODE
> +# LUA_COMPAT=( lua5_{1..3} )

s/_/-/

> +	eerror "No Lua implementation selected for the build. Please add one"
> +	eerror "of the following values to your LUA_TARGETS (in make.conf):"

Will add "or package.use" here.

> +# @FUNCTION: _lua_wrapper_setup
> +# @USAGE: [<path> [<impl>]]
> +# @INTERNAL
> +# @DESCRIPTION:
> +# Create proper 'lua' executable and pkg-config wrappers

Should be "proper Lua executables" - for dev-lang/lua we have got both
'lua' and 'luac', and for dev-lang/luajit we'll probably have 'luajit'
(have yet to see if invoking 'luajit' as 'lua' works).

> +# Check LUA_COMPAT for well-formedness and validity, then set
> +# two global variables:
> +#
> +# - _LUA_SUPPORTED_IMPLS containing valid implementations supported
> +#   by the ebuild (LUA_COMPAT - dead implementations),

Just say "minus" here, as it stands it is a bit confusing (at least to
me) because my first reaction is to read the - as a dash, not as an
arithmetic minus.

-- 
MS


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-09-04  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 13:37 [gentoo-dev] [PATCH] lua.eclass: initial implementation Marek Szuba
2020-09-03 13:37 ` [gentoo-dev] [PATCH 1/2] eclass: Add first version of lua.eclass Marek Szuba
2020-09-04  8:38   ` Marek Szuba [this message]
2020-09-06 17:13   ` Azamat Hackimov
2020-09-03 13:37 ` [gentoo-dev] [PATCH 2/2] profiles/desc: describe LUA_TARGETS Marek Szuba
     [not found] ` <c0cdb2ea-8932-72ca-1561-5dcb3df2880e@veremit.xyz>
2020-09-03 18:24   ` [gentoo-dev] [PATCH] lua.eclass: initial implementation Kent Fredric
2020-09-06 15:46 ` David Seifert
2020-09-07 14:27   ` Marek Szuba
2020-09-08 14:32 ` Marek Szuba
2020-09-08 15:04   ` Azamat Hackimov

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=a84cace2-33f1-7d25-687f-a9a503644e1f@gentoo.org \
    --to=marecki@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