I've today from scratch implemented a new vendor version tracker for OpenPKG-CURRENT development which now finally replaces the bi-daily regular openpkg-dev@openpkg.org mails -- which most of you do not read or don't want to read anyway ;-).
http://www.openpkg.org/development/tracker/ The advantages of the new vendor version tracking are: 1. It is split into a tracking (periodic cron job) and a reporting part (on-demand user interface). The tracking part stores its information into a database and the reporting part is a Web UI which renders the information on-the-fly (even while a current tracking is still in progress). 2. The tracking part caches all %track sections of the OpenPKG-CURRENT .spec files and this way is a lot faster (and consumes dramatically less server resources) as it no longer has to extract the sections over and over again (keep in mind that we have nearly 1000 packages and forking "openpkg rpm" 1000 times costs lots of resources!). 3. As the tracking information is stored in a database and old information is kept for a certain period of time, the reporting can be more useful by sorting the results according to the tracking repetition counter. New packages which were tracked already more often than others are sorted below the others. Failing trackings which occurred more often than others are sorted over the others. 4. As the reporting part is a Web UI, a click on a package directly lets one visit the tracked URL. This especially allows quicker error checking (packages which failed to track) and this way fixing of broken or out-dated %track sections. Those who want to contribute to OpenPKG-CURRENT, please feel free to visit the above URL at any time and commit package upgrades to our CVS according to the latest tracking results you can find there. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List openpkg-dev@openpkg.org