Jason Stubbs wrote:
To be honest, this is the part that I don't like the most. Integrating code
into portage to copy files here and there based on some predefined rules and
news readers reading and renaming files based on some predefined rules...
A filesystem based API just doesn't seem very robust to change.
I'd prefer that either the post-sync handling code is not integrated into
portage and portage just triggers some external script - or - portage exposes
an API (via python and bash) for accessing and updating news items. I'd
prefer the latter but I get the impression that most prefer the former.
- append message to /var/spool/mail/portage
alternative 1 (very very sober install):
- less /var/spool/mail/portage
- rm /var/spool/mail/portage
alternative 2 (sober install):
- vi /var/spool/mail/portage
alternative 3 (for those having `mail`, `mutt` or whatever that reads mbox)
- mail -u portage (program allows deletion)
alternative 4 (those that don't like mbox reading)
- either run mbox2mail or
- allow portage to write to a pipe to `mail` instead of append to
/var/spool/mail/portage (would be the best solution IMHO)
It doesn't have to be so complicated, IMHO. Most of the tools are
already there, because traditional unix systems had this notification
system built in. Imagine how nice you could benefit from a shell that
tells you you've got (new) mail if you log in as root. Appending in the
right format to /var/spool/mail/portage doesn't need an MTA either.
--
Fabian Groffen
Gentoo for Mac OS X Project -- Interim Lead
--
gentoo-dev@gentoo.org mailing list
