From: Marco Sirabella <marco@sirabella.org>
To: gentoo-lisp@lists.gentoo.org
Subject: [gentoo-lisp] www-client/nyxt ebuild & dependencies
Date: Sun, 21 Mar 2021 21:51:05 -0700 [thread overview]
Message-ID: <20210322045105.gho3xx7okpiubk54@Ridl3y> (raw)
[-- Attachment #1.1: Type: text/markdown, Size: 791 bytes --]
Hello,
I have just spend a bit of time setting up an ebuild for the [nyxt
browser](https://nyxt.atlas.engineer/). As this is written in common lisp, I've
also spent time creating / updating dependant ebuilds as well, and have ended
up with over 60 packages in `dev-lisp/` in my tree: <https://gitlab.com/mjsir911/my-overlay>
Would it be possible / is there interest to merge my updates & new ebuilds into
the [common lisp overlay](https://gitweb.gentoo.org/proj/lisp.git/)? I've
already stumbled upon some small bugs in the eclass and have made a
[PR](https://github.com/gentoo/gentoo/pull/20025) on the gentoo tree, but what
is the process for submitting new/updated ebuilds to the lisp overlay?
Thank you for your help, would appreciate any advice
--
Marco Sirabella
[-- Attachment #1.2: Type: text/plain, Size: 791 bytes --]
Hello,
I have just spend a bit of time setting up an ebuild for the [nyxt
browser](https://nyxt.atlas.engineer/). As this is written in common lisp, I've
also spent time creating / updating dependant ebuilds as well, and have ended
up with over 60 packages in `dev-lisp/` in my tree: <https://gitlab.com/mjsir911/my-overlay>
Would it be possible / is there interest to merge my updates & new ebuilds into
the [common lisp overlay](https://gitweb.gentoo.org/proj/lisp.git/)? I've
already stumbled upon some small bugs in the eclass and have made a
[PR](https://github.com/gentoo/gentoo/pull/20025) on the gentoo tree, but what
is the process for submitting new/updated ebuilds to the lisp overlay?
Thank you for your help, would appreciate any advice
--
Marco Sirabella
[-- Attachment #1.3: Type: text/html, Size: 1710 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2021-03-22 4:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210322045105.gho3xx7okpiubk54@Ridl3y \
--to=marco@sirabella.org \
--cc=gentoo-lisp@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