Warly wrote: > Oden Eriksson <[EMAIL PROTECTED]> writes: > > At present contrib are not signed. > > One of the idea for future is to have different keys and allow the user to select > which keys are valid for packages, for example: > > - Stable release > - Contrib stable release > - Development release > - Security updates >
The hope was that it would be implemented per-urpmi-source, so that for example if I was maintaining a bunch of desktops with 3rd-party software, I could associate a company key with the company urpmi source, and packages would be updated automatically (if I run urpmi --update from cron). PLF would also gain from this? > e.g. the user will have to explicitely select development key to be able to install > cooker packages on a stable release. > That's also a good thing, seen too many "cdbakeoven-1.8.9-5mdk doesn't work on 9.0" when I have -4mdk in club for 9.0 and -5mdk in cooker contrib ... > It is not likely that we have time to do this for 9.1. > Pity. Buchan -- |--------------Another happy Mandrake Club member--------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
