public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [Fwd: Re: [gentoo-dev] Package notices]
Date: Thu, 02 Sep 2004 18:17:02 -0400	[thread overview]
Message-ID: <1094163421.1055.77.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <1094155935.19504.40.camel@localhost>

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

On Thu, 2004-09-02 at 16:12, Eldad Zack wrote:
> On Thu, 2004-09-02 at 21:56, Alexander Gretencord wrote:
> > On Thursday 02 September 2004 20:46, Christian Gut wrote:
> > > another idea: simply hand them over to syslog. This way they get mailed
> > > to the admin and are there for later reference.
> > 
> > Just read Bug #11359 (http://bugs.gentoo.org/show_bug.cgi?id=11359). This has 
> > also been discussed there and is only an option for already installed 
> > systems.
> 
> > In short: The basic mechnism has to work without eMail and without syslog or 
> > any other fancy stuff. Just think of a bootstrap build, where no such thing 
> > is available.
> 
> What I had in mind could be deployed today, without needing to patch
> portage.
> Basically, it could be implemented using a new eclass or just adding the
> enotice function to eutils - I wouldn't want all the einfos logged,
> anyway. (patching notices? no thanks.)
> 
> What I would like, would be messages from packages like cacti.
> enotice itself will write into the file and emit an einfo.
> 
> This is what I had in mind:
> 
> # void enotice(char* message)
> #
> #    write informative message (with a newline) into notice log.
> #    also emits einfo.
> #
> enotice() {
> 	einfo "${*}"
> 
> 	if [ -n "${ENOTICE_DIR}" ]
> 	then
> 		# Not checking if it ${ENOTICE_DIR} exists since
> 		# install does stat and stops if it exists.
> 		install ${ENOTICE_DIR}
> 
> 		echo "${*}" >> ${ENOTICE_DIR}/${PF}
> 	fi
> 
>         return 0
> }
> 
> To make it work it only requires that ENOTICE_DIR would be set in
> make.conf.
> 
> It is also sandbox-friendly, since it is a regular file as far as
> portage concerns - and that also makes it binary-friendly. The notices
> will be included in the binary tbz2.
> 
> The external utility to read the messages is also pretty
> straight-forward to write.
> 
> I'd like to hear from other developers if they think it is useful and if
> they plan to use it...
> I would also like to go ahead and use it for any ebuilds I currently
> maintain.

It needs to be able to support the 3 levels of enotices: einfo, ewarn,
and ecrit.

-- 
Chris Gianelloni
Release Engineering - Operations/QA Manager
Games - Developer
Gentoo Linux

Is your power animal a penguin?

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

  reply	other threads:[~2004-09-02 22:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 20:12 [Fwd: Re: [gentoo-dev] Package notices] Eldad Zack
2004-09-02 22:17 ` Chris Gianelloni [this message]
2004-09-02 22:54 ` Thomas de Grenier de Latour
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=1094163421.1055.77.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@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