public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Eli Schwartz <eschwartz@gentoo.org>
Cc: "Anna (cybertailor) Vyalkova" <cyber+gentoo@sysrq.in>
Subject: Re: [gentoo-dev] Re: [PATCH 2/2] rebar3.eclass: add new eclass
Date: Mon, 15 Jul 2024 21:33:09 +0200	[thread overview]
Message-ID: <d72cb89b-45b8-4a3c-819f-4add23748802@gentoo.org> (raw)
In-Reply-To: <cee7638c-51b9-4c61-b8fd-336068bb09c8@gentoo.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1584 bytes --]

On 15/07/2024 04.39, Eli Schwartz wrote:
> On 7/10/24 11:38 PM, Anna (cybertailor) Vyalkova wrote:
>> On 2024-07-10 09:19, Florian Schmaus wrote:
>>> From: Florian Schmaus <flow@gentoo.org>
>>>
>>> Add a new eclass for dev-util/rebar:3, based on the work of Anna
>>> Vyalkova in ::guru (thanks!).
>>
>> There's also rebar3.eclass in lanodanOverlay, hereby CC-ing Haelwenn on
>> this.
>>
>>> The Erlang/OTP ecosystem is moving to Rebar3. Upstreams start to drop
>>> support for Rebar2, or at least consider it.
>
> I can't find the first part of this email thread, including the actual
> submission of the eclass for review to the mailing list. Was this a
> private conversation?

No it wasn't a private conversation. But unfortunately I've used the 
wrong 'from' address, my personal one instead of the @gentoo.org 
address, so the mails did not went through. However, I didn't notice it, 
since the mails appeared in my inbox (due to me being CC'ed).

I'll resend the patchset again, probably the first thing I'll do 
tomorrow. Sorry for the inconvenience.


> I notice that it *has* been committed by Flow to ::gentoo already, and
> your request for Haelwenn's feedback hasn't yet been answered.

I looked at the rebar3.eclass from the lanodanOverlay before pushing the 
new eclass, there seem to be no relevant differences from the one in 
::guru/::gentoo. Judging from the commit history of rebar3.eclass in 
lanodanOverlay and in ::guru, it appears that the one in ::guru used 
lanodanOverlay's rebar3.eclass as starting point.

- Flow




[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 21567 bytes --]

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

      reply	other threads:[~2024-07-15 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240710071916.116114-1-flo@geekplace.eu>
     [not found] ` <20240710071916.116114-3-flo@geekplace.eu>
2024-07-11  3:38   ` [gentoo-dev] Re: [PATCH 2/2] rebar3.eclass: add new eclass Anna (cybertailor) Vyalkova
2024-07-15  2:39     ` Eli Schwartz
2024-07-15 19:33       ` Florian Schmaus [this message]

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=d72cb89b-45b8-4a3c-819f-4add23748802@gentoo.org \
    --to=flow@gentoo.org \
    --cc=cyber+gentoo@sysrq.in \
    --cc=eschwartz@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