-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
# Bernd Waibel (2022-04-07)
# No consumers left. Superseded by dev-libs/imath[python]
# Removal in 30 days.
dev-python/pyilmbase
-BEGIN PGP SIGNATURE-
iQGTBAEBCgB9FiEExIg3+Emk70nqAQ2ybb4K1Uo7McYFAmJOvDBfFIAALgAo
Hello,
Right now we're keeping both email addresses (obligatory) and names
(optional) for downstream maintainers in metadata.xml. The way I see
it, there are three problems with that:
1. As noticed on IRC lately, a few devs haven't been listing their names
at all, resulting in these names being
> On Thu, 07 Apr 2022, Anna Vyalkova wrote:
> case ${EAPI} in
> - 6|7);;
> - *) die "EAPI ${EAPI:-0} unsupported (too old)";;
> + 6|7|8);;
> + *) die "${ECLASS}: EAPI ${EAPI:-0} unsupported (too old)";;
The "(too old)" part will look strange with EAPI 9. Just say that it's
On 2022-04-06 19:34, Rich Freeman wrote:
This is one of those low cost, low risk, high reward situations IMO.
*puts on Council hat*
The above pretty much covers my own opinion on the subject.
--
Marecki
OpenPGP_signature
Description: OpenPGP digital signature
From: Marco Sirabella
This is a bit of a roundabout way to do it, but since we want to pass
the results of `find` to a bash function, this is what we need to do.
All of these functions are a bit convoluted, I believe something similar
could be hacked together that looks like `find -type f -name
> On 7 Apr 2022, at 13:01, Anna Vyalkova wrote:
>
> From: Thomas Bracht Laumann Jespersen
>
> * Drop EAPI 0, 1, 2 workarounds
> * Move EXPORT_FUNCTIONS to end of file
> * Add required @USAGE on functions
> * Add _VIM_PLUGIN_ECLASS guard
>
> Bug: https://bugs.gentoo.org/830867
> Bug:
On Thu, Apr 7, 2022 at 11:42 AM Michał Górny wrote:
>
> Hello,
>
> Right now we're keeping both email addresses (obligatory) and names
> (optional) for downstream maintainers in metadata.xml. The way I see
> it, there are three problems with that:
>
> 1. As noticed on IRC lately, a few devs
> On 8 Apr 2022, at 00:07, Matt Turner wrote:
>
> On Thu, Apr 7, 2022 at 11:42 AM Michał Górny wrote:
>>
>> Hello,
>>
>> Right now we're keeping both email addresses (obligatory) and names
>> (optional) for downstream maintainers in metadata.xml. The way I see
>> it, there are three
