From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] drift: cron, emerge and mail
Date: Wed, 1 Nov 2006 12:04:05 +0000 [thread overview]
Message-ID: <20061101120405.4c6e409b@krikkit.digimed.co.uk> (raw)
In-Reply-To: <4547692B.9050804@ilievnet.com>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On Tue, 31 Oct 2006 17:18:03 +0200, Daniel Iliev wrote:
> Let me explain what I'm trying to do. I want to automate "emerge --sync
> && emerge -DuNv world" with a cron job
I'm not sure automating emerge -u world is good idea. I have a cron task
that does
emerge --sync
emerge -upvDN world | mail
emerge -ufDN world
Then I read the mail and decide on the updates before anything is merged.
> and to receive mails for the
> portage activities. I really don't need all the gcc output. I only need
> the portage "info warn error" messages
PORTAGE_ELOG will do this for you.
> in order to know if I have to do "dispatch-conf",
It won't do this, but "find $(portageq config_protect) -name '._cfg*'"
will. Or you could put it in a script with
if [ "$(find $(portageq config_protect) -name '._cfg*' | wc -l)" != "0" ]
then
echo "Run dispatch-conf"
fi
> if some package has failed and if there is some
> important note about changes in the structure/functionality of a given
> package.
PORTAGE_ELOG will tell you that.
--
Neil Bothwick
Madness takes its toll. Exact change, please.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-01 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 20:28 [gentoo-user] PORTAGE_ELOG Daniel Iliev
2006-10-31 8:59 ` Arnau Bria
2006-10-31 14:06 ` Daniel Iliev
2006-10-31 14:15 ` Bo Ørsted Andresen
2006-10-31 14:39 ` Daniel Iliev
2006-10-31 14:42 ` Neil Bothwick
2006-10-31 15:18 ` [gentoo-user] drift: cron, emerge and mail Daniel Iliev
2006-11-01 12:04 ` Neil Bothwick [this message]
2006-11-01 13:15 ` [gentoo-user] [SOLVED] " Daniel Iliev
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=20061101120405.4c6e409b@krikkit.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@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