From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-proxy-maint@lists.gentoo.org
Subject: Re: [gentoo-proxy-maint] [PATCH v2] net-misc/lagrange: initial import
Date: Tue, 15 Jun 2021 21:28:05 +0300 [thread overview]
Message-ID: <9f1e7033-0351-0b42-6401-e817dfa3c28c@gentoo.org> (raw)
In-Reply-To: <20210615182205.8991-1-cyber+gentoo@sysrq.in>
[-- Attachment #1.1: Type: text/plain, Size: 1223 bytes --]
On 15.6.2021 21.22, Anna Vyalkova wrote:
> Signed-off-by: Anna Vyalkova <cyber+gentoo@sysrq.in>
> ---
> Version bump to 1.5.2
>
> net-misc/lagrange/Manifest | 1 +
> net-misc/lagrange/lagrange-1.5.2.ebuild | 42 +++++++++++++++++++++++++
> net-misc/lagrange/metadata.xml | 33 +++++++++++++++++++
> 3 files changed, 76 insertions(+)
> create mode 100644 net-misc/lagrange/Manifest
> create mode 100644 net-misc/lagrange/lagrange-1.5.2.ebuild
> create mode 100644 net-misc/lagrange/metadata.xml
Hey,
Saw this earlier today but couldn't reply before this.
Lagrance is already in the GURU repository, and we're very reluctant in
adding new packages through proxy-maint to ::gentoo repo at the moment
due to being severely overworked. Basically if it's not a required dep
for an existing package, or if no dev has personal interest in it, its
only place it can nourish is ::guru. Where we port required deps or
popular packages, which lagrance doesn't seem to be, occassionally into
::gentoo.
And we'd much prefer getting Github PRs - but I guess you saw no new
packages are merged from GH? All the info is printed in a new package PR
about GURU too.
-- juippis
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
prev parent reply other threads:[~2021-06-15 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 16:11 [gentoo-proxy-maint] [PATCH] net-misc/lagrange: initial import Anna Vyalkova
2021-06-15 18:22 ` [gentoo-proxy-maint] [PATCH v2] " Anna Vyalkova
2021-06-15 18:28 ` Joonas Niilola [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=9f1e7033-0351-0b42-6401-e817dfa3c28c@gentoo.org \
--to=juippis@gentoo.org \
--cc=gentoo-proxy-maint@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