public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: freijon@pm.me
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] shell-completion.eclass
Date: Tue, 11 Jul 2023 12:36:56 +0000	[thread overview]
Message-ID: <GMKs4Yd8E6KTLjrlYL_KYyvjCAachPWdkiut6qx5Q0R6aoJsgpypLDxVqTM6bajM4N072Nk4V70vXUkbC_IuLCMTOsv-1kM1ys0GovrKQQI=@pm.me> (raw)


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

On July 2nd we had a discussion on #gentoo-guru on IRC about adding shell-completion.eclass to ::gentoo. It's already well established on GURU and used in 23 ebuilds. It's basically bash-completion-r1, but also includes `zsh` and `fish` with standard install locations for the completion scripts.
For the raison d'être, see: https://bugs.gentoo.org/843875

Check out the eclass here: https://gitweb.gentoo.org/repo/proj/guru.git/tree/eclass/shell-completion.eclass

I hereby ask for a code review and to add this eclass to the ::gentoo repository.

I offer to continue maintaining the eclass and Florian Schmaus (Flow) offered to co-maintain the eclass.

Please let me know your thoughts about this.

[-- Attachment #1.1.2.1: Type: text/html, Size: 1563 bytes --]

[-- Attachment #1.2: publickey - freijon@pm.me - 0x259C4FF5.asc --]
[-- Type: application/pgp-keys, Size: 3068 bytes --]

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

             reply	other threads:[~2023-07-11 12:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 12:36 freijon [this message]
2023-07-14  9:44 ` [gentoo-dev] Re: shell-completion.eclass freijon

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='GMKs4Yd8E6KTLjrlYL_KYyvjCAachPWdkiut6qx5Q0R6aoJsgpypLDxVqTM6bajM4N072Nk4V70vXUkbC_IuLCMTOsv-1kM1ys0GovrKQQI=@pm.me' \
    --to=freijon@pm.me \
    --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