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:31:14 -0800	[thread overview]
Message-ID: <2841808.J3EoXrtVBX@reaper> (raw)
In-Reply-To: <241902c5-41c5-82a8-89bf-12de85752358@gentoo.org>

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

On Sunday, December 16, 2018 2:18:33 PM PST Toralf Förster wrote:
> On 12/15/18 3:00 AM, Georgy Yakovlev wrote:
> > that should be enough to provide a bit more to initial information without
> > going crazy and clobbering output too much.
> > 
> > Thoughts?
> 
> At least for the tinderbox image issues I was asked by devs in the past to
> include bits for the following software in #comment0:
> 
>   cat << EOF >> $issuedir/issue
> gcc-config -l:
> $(gcc-config -l                   )
> $( [[ -x /usr/bin/llvm-config ]] && echo llvm-config: && llvm-config
> --version ) $(eselect python  list 2>/dev/null)
> $(eselect ruby    list 2>/dev/null)
> $(eselect rust    list 2>/dev/null)
> $( [[ -x /usr/bin/java-config ]] && echo java-config: && java-config
> --list-available-vms --nocolor ) $(eselect java-vm list 2>/dev/null)
> 
> ...
Actually after conversation with you on some rust related bug It occurred to 
me that there should be a more central location for similar info, so every 
reported bug that has --info output can show it right away, not only tinderbox 
bugs.
-- 
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:31 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
2018-12-16 22:18 ` Toralf Förster
2018-12-16 22:31   ` Georgy Yakovlev [this message]

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=2841808.J3EoXrtVBX@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