On Tue, 2007-07-17 at 12:49 -0400, Joe Smith wrote: > All the information is there already, it just isn't tied together and > presented effectively. The only piece that's missing (in some cases) > is a short summary of the purpose for the update. Yes, the lack of that information could easily be provided by the maintainers (it's called typing), but it seems that only some bother. > The only missing piece is a key or update ID that can tie an update > package to the update information, so the update agent can retrieve > the info to present. Sounds like what you want is some sort of cron script that does a "yum check-update", parses the output, then does something like "yum info <list of packages>" to get information just on what's related to you, and presents you with the output. There's one technical problem I can already see with that - the output from "yum check-update" only shows what's new for what you've already got. Additional new dependencies, or package replacements, aren't worked out for the results. -- [tim@bigblack ~]$ rm -rfd /*^H^H^H^H^H^H^H^H^H^Huname -ipr 2.6.21-1.3228.fc7 i686 i386 Using FC 4, 5, 6 & 7, plus CentOS 5. Today, it's FC7. Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
