On Sat, Nov 22, 2003 at 04:09:04PM -0500, Christopher Faylor wrote: >Unless there is a real need for this service, I don't see a reason to >advertise out-of-date packages publicly. There is no requirement that >every package in the cygwin distribution be absolutely up-to-date. IMO, >sending out something like this gives the impression that it is >something to strive for. I can imagine some of our more clue challenged >users latching onto this message and assuming that their problem with >patchutils is due to the fact that it is now advertised as being out of >date. > >Also, I don't necessarily want to have to repeatedly defend a decision >to not use the latest version of, say, flex every time this message is
On thinking about this some more, I think I'm approaching this from the wrong direction. Being notified of package updates would be a nice service if it was opt-in and configurable somehow. Personally, I already have a mechanism that I've been using for years to notify me when a package changes, not that I use it for everything that I maintain. However, it's likely that others would appreciate this service. So one solution is to create a database on sources.redhat.com with package information in it that package maintainers can control. And, I could adapt my current program to send out update notices as new packages become available -- to those people who are interested in getting the notices, of course. cgf