On Monday 03 October 2005 11:48, Pascal Bleser wrote:
James Ogley wrote:
Thing is that that's for sw_single and the same doesn't also apply for online_update - it can only have one source of packages at a time, and to say to users: "Sometimes you will want to run the Online Update option in YaST to get the latest updates, but sometimes you'll want to run the Software Management option is little counter-intuitive.[2] I would like to suggest it be consolidated into a single component that handles adding and removing packages, as well as updating from all YaST sources, and SUSE update trees. That's all I'm going to say about it now, any thoughts?
I second that. Actually I would propose to re-think the current concept of YaST2's Software Management module. To me, it should be an aggregator of package information from various sources: - SUSE repositories - supplemental, if checked - 3rd party repositories, if checked - Online Update (or not, if it is obsoleted by YaST2 Software Management)
jfyi, we do think about such a tool, but it will not happen within the next 6 month from the SUSE side. Maybe we could create some temporary solution, simply using a small application around the http://kstuff.org/ mechanism. A client would be provided already via the kdelibs, we only need to figure out how to setup such a server (but I have some contacts how can answer this ;)
I'd also suggest to define some metadata format to "mechanize" that information, and all the 3rd party packagers would have to provide such metadata to be integrated into the "YaST2 Software Central" (or whatever). XML seems well-suited for that purpose (also because it can be directly transformed to, say, HTML).
That metadata could include things like: - package name, package version, release (obviously) - release scope: new features, bugfix, security fix - version state: beta, stable - changelog information - description - link to project website - screenshot(s)
Screenshot(s) may sound futile, but... how about providing some kde-apps.org-like interface ? See for yourself: http://kde-apps.org (but I guess everyone on this list knows that site already ;)) Actually that's kde-apps.org and freshmeat.net alike.
Note that e.g. the freshmeat.net project metadata (XML) can already be used for most of the stuff above. I do so already, but only for part of the information (see my previous post on the list about my little script and emacs macro that fetches that data).
Obviously, and that's probably the reason why this will never happen, implement all of this requires a major YaST2 overhaul, especially as far as the Software Management module is concerned :\
yes, but this will happen anyway ;)
In fact, is anyone else on this list? ;)
Yep ;)
m2 bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de