Le mardi 21 décembre 2010 à 06:48 -0500, andre999 a écrit : > nicolas vigier a écrit : > > > > On Tue, 21 Dec 2010, andre999 wrote: > > > >> > >> We could have a structure something like this : > >> > >> Primary key : name of package > >> > >> Other fields, 1:1 relation : > >> - package rpm category (+ subcategory, if any) > > > > What is the category ? > > I meant the rpm group tag
That's duplication with the content of the rpm, that is useless for our use cases. If you want a package database, there is sophie.zarb.org ( and its rewrite, sophie2 ). > >> - repository > >> - etc > >> > >> Other fields, 1:N relation : > >> - Packager nickname + packager status (primary maintainer, trainee or > >> whatever) + real name + email > >> (The last 2 items could be in a separate table keyed by nickname.) > > > > Why duplicate infos from ldap database ? And why would we need that in > > maintainers db ? > > Basically info in the packager wiki page. > what ldap database ? The ldap holding central authentication information ( ie, name, email, group, etc ), as mentioned on http://blog.mageia.org/?p=173 ( among others, we also discussed this quite a bit on sysadmin ). -- Michael Scherer
