From: Eldad Zack <eldad@gentoo.org>
To: Gentoo-Dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Package notices
Date: Wed, 01 Sep 2004 22:42:57 +0300 [thread overview]
Message-ID: <1094067776.19503.9.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
Hey Guys,
I've got an idea to implement package notices, as opposed to
outputing these important messages to stdout using e{info,warn,error}.
The idea is VERY simple: write the message to a file (say,
/var/portage/notices/{P}) and have a utility to read and delete these
messages. Maybe even build this functionality into etc-config.
(Maybe mail these messages to a configured address?)
For ease-of-use I propose adding a simple wrapper command ("enotice" or
"notice") that would take care of writing into the correct file.
If this looks like a good idea I'll move on and punch out the matching
code.
Comments? Ideas?
--
Eldad Zack <eldad@gentoo.org>
Key/Fingerprint at pgp.mit.edu, ID 0x96EA0A93
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-09-01 19:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 19:42 Eldad Zack [this message]
2004-09-01 21:05 ` [gentoo-dev] Package notices William Hubbs
2004-09-01 22:01 ` Thomas de Grenier de Latour
2004-09-02 16:46 ` purslow
2004-09-02 18:06 ` Anton Starikov
2004-09-02 19:59 ` N. Owen Gunden
2004-09-02 18:46 ` Christian Gut
2004-09-02 18:56 ` Alexander Gretencord
-- strict thread matches above, loose matches on Subject: below --
2004-09-02 20:12 [Fwd: Re: [gentoo-dev] Package notices] Eldad Zack
2004-09-03 5:10 ` [gentoo-dev] Package notices Nicholas Jones
2004-09-03 14:00 ` Pablo Villalba
2004-09-03 12:47 ` Jason Stubbs
2004-09-03 15:10 ` Eldad Zack
2004-09-03 14:15 ` Jason Stubbs
2004-09-03 16:15 ` Eldad Zack
2004-09-04 12:55 ` Eldad Zack
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=1094067776.19503.9.camel@localhost \
--to=eldad@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