> They have the same format as the Red Hat Linux and Red Hat Enterprise
> Linux announcements instead, no?
> * Most other distros do it our way (only Fedora Project differs that I know
> of, though there are probably others).
Perhaps. My point is one of utility, not compatibility. I was
pointing out that FP does it this way to show what I like, not to
raise a compatibility point.
However, there is a compatibility point, now that you mention it.
People using this service are coming off of FP, not off some other
distro. It would be good to keep the same form of communication,
particularly where some people use automated means to process the
information. Matthew Miller mentioned to me that he also processes
those messages with scripts.
> > The announcements are not of a down-to-the-minute,
> > time-critical nature.
> I think some people would disagree with that.
If you are referring to people working on the project, I can see the
need for response/attention in under a day. For people using the
service in its recommended form (i.e., nightly yum updates), the
advisories are not so urgent, assuming their update systems are
working.
> I don't like it, for the following reasons:
> * More work for the people cutting updates (unless they can automate this
> more for the future)
> * More work for me (I update the advisories on the web site from the e-mails
> sent to the announce list)
These show a developer's point of view, not a user's (though on a
volunteer project with limited resources, it may be defensible to put
developers' needs over users').
> * Too many e-mails (and sometimes digest formats just aren't desirable).
As a user, you'd like to be able to filter out the ones that are for
you, and preferably also check that you got the updates in an
automated way (by the way, I said in my post that I'd attach the
script and didn't, so see below).
Jesse Keating said that the emails are sent automatically, written by
Python scripts. It wouldn't be too outrageous to grab the scripts
from FP and have them post to a second list (or even a list per
release). People would be able to subscribe to either and everyone
would be happy. My impression is that these scripts should not be
hard to maintain, particularly if you're grabbing one set from FP
rather than writing them yourselves.
--jh--
cd ~/bin
cat > updchk << EOF
#! /bin/sh
# run this, cut-n-paste the announce-list's daily archive summary
# to it, hit return for good measure, and type ^D once
rel=`awk '{print $4}' /etc/fedora-release`
rpm -q `grep "Fedora Core $rel Update:" | sed -e 's/.*Update: //' -e 's/ .*//'`
EOF
chmod 755 updchk
--
fedora-legacy-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-legacy-list
