On Fri May 30, 2003 at 06:30:03PM -0400, Brian J. Murrell wrote: > > In terms of release numbers etc, I normally decrement (ie 1mdk->0.9mdk as > > I did with kdirstat) the release when it goes into Club, > > But then how does one get the update if they are running 1mdk (to use your > example)? Urpmi will see that what's in Club is lower in version number > and not do an update when in reality one might want to update. > > What I do here locally, is to use decimal increments > last Mandrake > released and < what will be their next release. Again to continue > your example, if they release (say into 9.1) foo-1.0-1mdk, if I want to > update that, I make mine foo-1.0-1.1mdk, and then their next release will > be foo-1.0-2mdk. Urpmi is happy to update all of these in the right > order.
This is a bad idea. If foo-1.0-1mdk is in 9.1 and there is a security update, I will use foo-1.0-1.1mdk, not foo-1.0-2mdk. A full increment is only done in cooker, not in updates. -- MandrakeSoft Security; http://www.mandrakesecure.net/ Online Security Resource Book; http://linsec.ca/ "lynx -source http://linsec.ca/vdanen.asc | gpg --import" {FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
pgp00000.pgp
Description: PGP signature
