Dan Brown wrote: > OK, so we know (or at least, have been told) > that a blade is simply a .noarch.rpm with a set > of strict dependencies for the packages that need > to be installed. We have the .src.rpm files for > the existing "official" blades. And really, > that's about all we have. Obviously, there's > at least one critical step missing: where do they > go?
Dan, since the source is available, I wonder if someone is able to look over the source code and tell how the system checks for blades (know where to go for updates) and then modify it to allow a person to enter specific URL's to check for updated blades. I for one would like to have the ability for the blades panel to check the contributors sites in addition to Mitel's site. >From what I can tell, the update-system DevInfo has created is fine and dandy, but it requires you to have the updated packages already and know what packages have updates to them. I really like the new Redhat 7.3 system update checker that runs automatically and alerts you if there are new updates to be applied. It would be nice if such a beast were made that would sit at the main screen console and tell you if there are any updates available. It could be set to poll once a day, and the sysadmin could designate the time of day it should check for updates. Just my two cents... Tom Carroll Dataware Computers -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
