From: Brian Evans <grknight@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] Last rites: app-portage/layman
Date: Fri, 19 May 2023 14:30:11 -0400 [thread overview]
Message-ID: <9147421e-10a0-28e6-0b24-47533add729e@gentoo.org> (raw)
In-Reply-To: <CAJ0EP4362qUttGsCisG0t9xuPv3=yWf_6bBX+raokT5P9TaF_A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]
On 5/19/2023 1:51 PM, Mike Gilbert wrote:
> On Thu, May 18, 2023 at 7:07 PM Sam James <sam@gentoo.org> wrote:
>>
>>
>> Alexe Stefan <stefanalexe48@gmail.com> writes:
>>
>>> Layman is still a convenient way of managing overlays. It still works
>>> as intended.
>>> Is there any way for it to be kept in the repos?
>>
>> Is there an issue for you with using eselect-repository, which is
>> actively maintained and doesn't depend on unmaintained software
>> (pyGPG and g-sorcery)?
>
> Is anyone aware of an alternative for "layman -i repo_name"? I use
> that on occasion to find overlay maintainers when assigning bug
> reports.
>
For repository owners, there's a simple way using xmllint (from the
common libxml2 package):
xmllint --xpath "//repo[name='mysql']/owner"
~/.cache/eselect-repo/repositories.xml
Trade out the name as necessary. Needs a copy of repositories.xml
locally which eselect-repository often caches. (Time is defined by
REMOTE_LIST_REFRESH in /etc/eselect/repository.conf default of 2 hours.)
Brian
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-05-19 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 22:34 [gentoo-dev] Last rites: app-portage/layman David Seifert
2023-05-18 23:00 ` [gentoo-dev] Re: [gentoo-dev-announce] " Alexe Stefan
2023-05-18 23:07 ` Sam James
2023-05-19 6:49 ` Mickaël Bucas
2023-05-19 17:51 ` Mike Gilbert
2023-05-19 18:30 ` Brian Evans [this message]
2023-05-22 10:50 ` Alexe Stefan
2023-05-22 11:18 ` Adrian Schollmeyer
2023-05-22 10:53 ` Alexe Stefan
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=9147421e-10a0-28e6-0b24-47533add729e@gentoo.org \
--to=grknight@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