From: Anton Starikov <antst@ifm.liu.se>
To: Gentoo Devt <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Package notices
Date: Thu, 02 Sep 2004 20:06:47 +0200 [thread overview]
Message-ID: <41376137.1050608@ifm.liu.se> (raw)
In-Reply-To: <20040902164637.GC3690@sympatico.ca>
At least they can be collected in some buffer and dumped to the output
stream after process of emerging. It can be realy helpfull, when you
emerge more than one package at time.
purslow@sympatico.ca wrote:
> 040901 Eldad Zack wrote:
>
>>I've got an idea to implement package notices,
>>as opposed to outputing these important messages to stdout
>>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.
>
>
> as a mere user, i wd find this definitely helpful.
> at present, important warnings etc can get lost in the copious Emerge output.
>
> keep it simple: such msgs sb written to appropriately-named files
> in some obvious subdirectory under /usr/portage ;
> leave it to the user to delete them whenever s/he decides;
> make it an option in /etc/make.conf .
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-02 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 19:42 [gentoo-dev] Package notices Eldad Zack
2004-09-01 21:05 ` 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 [this message]
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=41376137.1050608@ifm.liu.se \
--to=antst@ifm.liu.se \
--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