From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] automated extended information gathering
Date: Sun, 8 Jul 2007 01:10:15 +0200 [thread overview]
Message-ID: <20070708011015.cfaa28c5.genone@gentoo.org> (raw)
In-Reply-To: <200707071743.44605.vapier@gentoo.org>
On Sat, 7 Jul 2007 17:43:44 -0400
Mike Frysinger <vapier@gentoo.org> wrote:
> often times when i get a bug report about certain packages, there's
> information about that package that i usually ask for ... i wonder if
> this can be automated
>
> perhaps extend the syntax of profiles/info_pkgs:
> <atom> [command to pass to system()]
> sys-libs/glibc /lib/libc.so.6
>
> then when people run `emerge --verbose --info`, for every atom
> matched as installed, it'd automatically run the listed command and
> display the output
>
> useful ? security issue waiting to explode ? crazy wacky monkey ?
I see several problems with that approach:
1) adding a secondary purpose to info_pkgs, history has shown that we
should avoid such things (think packages file)
2) as a consequence of 1), I assume people would add packages to
info_pkgs only for the new purpose, cluttering regular --info output
with irrelevant information
3) sounds more like something that should only trigger in `emerge
--info foo`
4) likely not backwards compatible
5) considering 3), I'd rather see such information be specified by
ebuilds somehow, not a global file (think about overlays). Maybe by
installing a script in a specific location or so.
Marius
--
Marius Mauch <genone@gentoo.org>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-07-07 23:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 21:43 [gentoo-dev] automated extended information gathering Mike Frysinger
2007-07-07 22:58 ` Petteri Räty
2007-07-07 23:10 ` Marius Mauch [this message]
2007-07-07 23:24 ` Kevin Lacquement
2007-07-07 23:41 ` Mike Frysinger
2007-07-08 0:21 ` [gentoo-dev] " Duncan
2007-07-08 0:52 ` [gentoo-dev] " Kent Fredric
2007-07-08 3:19 ` Mike Frysinger
2007-07-08 3:31 ` Kent Fredric
2007-07-08 3:56 ` Mike Frysinger
2007-07-08 4:42 ` Kent Fredric
2007-07-08 5:01 ` Mike Frysinger
2007-07-08 5:12 ` Kent Fredric
2007-07-08 11:04 ` [gentoo-dev] " Steve Long
2007-07-08 10:45 ` [gentoo-dev] " Mike Auty
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=20070708011015.cfaa28c5.genone@gentoo.org \
--to=genone@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