From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] adding more entries to profiles/info_pkgs
Date: Sat, 15 Dec 2018 21:43:11 +1300 [thread overview]
Message-ID: <20181215213953.4638007d@katipo2.lan> (raw)
In-Reply-To: <3093185.GVz38FWURC@ws>
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
On Fri, 14 Dec 2018 18:00:55 -0800
Georgy Yakovlev <gyakovlev@gentoo.org> wrote:
> Good candidates for adding to that file are:
>
> virtual/rust
> llvm ?
> dev-util/meson
> dev-util/ninja
I'm really not sure these are widespread enough to justify putting
those details in the ouput of every emerge --info.
Instead, it seems to make more sense to have them displayed via the
pkg_info() function[1], which can be provided by eclasses where need be.
1: https://devmanual.gentoo.org/ebuild-writing/functions/pkg_info/index.html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-15 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 2:00 [gentoo-dev] [RFC] adding more entries to profiles/info_pkgs Georgy Yakovlev
2018-12-15 8:43 ` Kent Fredric [this message]
2018-12-15 11:57 ` Mikle Kolyada
2018-12-16 22:14 ` Georgy Yakovlev
2018-12-16 22:18 ` Toralf Förster
2018-12-16 22:31 ` Georgy Yakovlev
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=20181215213953.4638007d@katipo2.lan \
--to=kentnl@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