On Sat, Aug 03, 2002, T.J. Yang wrote: > May I see the script for generating this report ? > Looks like this Version tracking report is doing > some sort of auto-bulid. > > Right now I am doing it the KISS way like this for two times > [...] > Check out http://www.tu-ilmenau.de/~gomar/stuff/vcheck/. The perl script just calls a program called 'vcheck' to make it easier to know which packages are in need of updating. It is our way to KISS, but I don't think it will help you with the dependencies. To do a build world or whatever like you want, we have another perl script called src2make which generates a makefile for building OpenPKG packages unattended and in the right order. However, this script is half broken at the time. I'm going to fix it as soon as we can get the bootstrapper working perfectly for the upcoming OpenPKG 1.1 release. One thing just follows another, as you can see.
> Also why there are different version of same > pakage in current/SRC ? I have to manually > pick the new version. is is not good for > back build. > The intention of OpenPKG is to offer release quality packages as a whole environment to pick and choose from. This happened once with OpenPKG 1.0 and will happen again with OpenPKG 1.1, at which time you can download from release/1.1/SRC instead of current/SRC. The latter directory is intended for testing and keeping up to date inbetween OpenPKG releases. If things go as we hope the interval of development between releases will shrink soon, making the 'current'-grade packages less needed. In any case, you will see packages there from multiple versions, dates, and even qualities (check out the field 'Distribution' in OpenPKG .spec files - sometimes it is REL and sometimes EXP). Regards, Michael -- [EMAIL PROTECTED] Development Team, Application Services Cable & Wireless Deutschland GmbH
msg00782/pgp00000.pgp
Description: PGP signature
