I have written a script, support/fix-puppy-dbs, which examines the local 'Packages-puppy-*' package database files, makes sure they have correct entries, and also checks with the 'Packages-puppy-*' files on ibiblio.org and even checks that the packages actually exist on ibiblio.org.
This script is called automatically when the '0setup' script is run.
A technical note:
Ibiblio has files 'Packages-puppy-2-official', 'Packages-puppy-3-official', 'Packages-puppy-4-official' and 'Packages-puppy-5-official' and these are also local for Woof to access.
For building Ppup for the Puppy4 series, there is a special local file 'Packages-puppy-4xx-official' -- this is not at ibiblio.org, in Woof only. This files defines the set of packages that Puppy will be built from.
For the Ppup Pupy2 series, the equivalent is 'Packages-puppy-2xx-official'.
One of the things that the 'fix-puppy-dbs' script does is make sure the entries in the 'Packages-puppy-2xx-official' and 'Packages-puppy-4xx-official' have correct entries and are synchronised with the other 'Packages-puppy--official' files.
Comments:Posted on 22 Jun 2009, 10:35 by dogone
As to your forum comment regarding alpha numbering, I think version numbering is the better strategy. "Alpha 471" could be the 53rd alpha for all anyone knows. The scheme also avoids the distinction between alpha and beta. Of course if you love Latin...