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: [gentoo-dev] Slotted Lua: eclass migration status
Date: Sat, 28 Nov 2020 20:09:57 +0100	[thread overview]
Message-ID: <d7243ef5-31cb-8434-7cc6-74f9c9a8f0ed@gentoo.org> (raw)


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

Let me begin by giving my sincere thanks to everyone who has already 
taken time in the last several weeks to either migrate their 
Lua-dependent packages to lua{,-single}.eclass or otherwise made sure 
said packages will not block migration to slotted dev-lang/lua. Your 
efforts have been VERY much appreciated!

On the less positive side, the slotted-Lua tracker bug [1] has still got 
119 open "migrate to lua eclasses" tickets attached to it. You can find 
the complete list at [2]. While the migration of some of depends on 
various Lua modules which have not themselves been migrated (from a 
glance at the dependency tree, it seems dev-lua/lpeg and 
dev-lua/LuaBitOp are the ones we need the most urgently), the vast 
majority of these packages depend on dev-lang/lua only i.e. could 
already be migrated.

[1] https://bugs.gentoo.org/657722
[2] https://dev.gentoo.org/~marecki/open_lua_eclass_bugs-20201128184637.txt

-- 
MS


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

             reply	other threads:[~2020-11-28 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-28 19:09 Marek Szuba [this message]
2020-11-30 11:43 ` [gentoo-dev] Re: Slotted Lua: eclass migration status Marek Szuba

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=d7243ef5-31cb-8434-7cc6-74f9c9a8f0ed@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