Le mer 08/10/2003 � 15:05, Pierre Jarillon a �crit : > Le Mercredi 8 Octobre 2003 09:18, Vedran Ljubovic a �crit : > Yes your idea is very good and ergonomic. As GC said, "There would take very > much diskspace, especially screenshots!" > To avoid this, it could be useful to create a database hosted by Mandrake:
several problems : 1�/ db loads form mdk 2�/ need an internet connection we'd better use a local lighweight db like sqlite ( http://www.sqlite.org/ , http://www.sqlite.org/faq.html ). The first time rpmdrake is launched or when a hdlist is modified, rpmdrake rebuild the database and then do everything after on this database. The difficulty is to sync urpmi/rpmdrake DB with rpm DB ( but you could think about the fact that when an rpm is inserted or deleted from rpm DB, rpm automatically update rpmdrake DB accordingly ). To my mind this could resolve our speed problems with hdlist computations at rpmdrake start and when performing queries. I could hope that sqlite may be far faster. Perl bindings exist -> http://www.sqlite.org/cvstrac/wiki?p=SqliteWrappers If the Db is corrupt, just rebuild it ! ( hdlist computation + sync with rpm DB ) > Main table > Name : generic name of the software (primary key) > class : program, plugin... > usage : Recommended, Common, Deprecated. > description : default description in english > Localization table > Name : generic name of the software (Foreign key) > langage : fr, en, ... > description : the description of the package > author : author of the description > date : automatic. The latest will be shown. > link-home : home page of the project (ex: > http://fr.openoffice.org/) > screenshot : localized screenshot (name or URL of the file) > Groups table > Name : generic name of the software (Foreign key) > group : Rpm-Group (a software can belongs to several groups) > > This is only a draft. I can participate to a full implementation of a > database. > Then it would be easy to export a localized description of each package if it > exists. > > I suggest to use the club and contributors (people having an account) to fill > the localized texts and screenshots. > > This database should be the first in the world and give the leadership to > Mandrake because people want to be helped in their own language to find > the software they need. TRUE ! > My proposition of a database don't breaks RpmDrake, it is only a complement > and is along with your ideas. IMHO, it is a good way for a smooth evolution. > RpmDrake can show the localized description if it exists without breaking it. --- Chez Leon, on est electricien d'ampere en fils, on a seulement les mains balladeuses.
