public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Georgy Yakovlev <gyakovlev@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] adding more entries to profiles/info_pkgs
Date: Sun, 16 Dec 2018 14:14:37 -0800	[thread overview]
Message-ID: <3825460.EZnp4yrIHk@reaper> (raw)
In-Reply-To: <61717838-74b6-7e0c-4482-fe56c62e94ed@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

On Saturday, December 15, 2018 3:57:02 AM PST Mikle Kolyada wrote:
> On 15.12.2018 5:00, Georgy Yakovlev wrote:
> > Hi,
> > 
> > while lurking on bugzilla lately I noticed that package part of
> > "emerge --info" output may be lacking in some cases.
> > 
> > Good candidates for adding to that file are:
> > 
> > virtual/rust
> > llvm ?
> > dev-util/meson
> > dev-util/ninja
> > 
> > that should be enough to provide a bit more to initial information without
> > going crazy and clobbering output too much.
> > 
> > Thoughts?
> > 
> > Regards,
> > Georgy Yakovlev
> > Gentoo Linux Developer
> 
> They all are not way too much spread, especially rust.
> 
> Do not think it worth to include them.
> 
> meson can be reconsidered later, as more and more people are using this one.

meson and ninja come in pair, and:
systemd already depends on both
openrc wants to switch to meson.
many xorg parts depend on meson
mesa & co depends on meson
cmake-utils.eclass defaults to ninja as default makefile generator for EAPI=7

those are damn  good reasons for inclusion, those tools becoming essential.
and it's only couple of lines of text, not a big deal.
and the lines are not shown if package in question is not installed.

having rust in output of initial  --info also can be quite handy as recent 
cargo/rust issue showed but yeah, pkg_info probably could deal with that for 
now at least. not a very popular ebuild function, never knew it existed. 
Thanks  Kent for pointing it out.




-- 
Georgy Yakovlev
Gentoo Linux Developer

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-12-16 22:14 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
2018-12-15 11:57 ` Mikle Kolyada
2018-12-16 22:14   ` Georgy Yakovlev [this message]
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=3825460.EZnp4yrIHk@reaper \
    --to=gyakovlev@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