[Mageia-dev] Dev Team Call To Action...

Maarten Vanraes maarten.vanraes at gmail.com
Fri Jan 28 01:59:15 CET 2011

Op donderdag 27 januari 2011 23:38:36 schreef Samuel Verschelde:
> Le jeudi 27 janvier 2011 01:17:26, Maarten Vanraes a écrit :
> >  - mageia would then package AppStream in the distro. (Nothing is being
> > 
> > said as being used by default: Note that AppStream only does
> > Applications, while eg: rpmdrake installs packages).
> Note that "AppStream" is not the name of a piece of software, but the
> codename for a project that relies on various components (packagekit, OCS,
> applications metadata...). We *may* use the Ubuntu Software Center (which
> should be using packagekit as a back-end instead of apt soon, hopefully),
> but we could also choose to develop our own Software Center or improve
> existing tools (though it would probably require a lot of work).

I just hope we can have an AppInstaller that is called something without any 
distro's name in it. :-)

> > So this leaves:
> >  - PHP for mageia-app-db
> For mageia-app-db, we can use help on various subjects
> (internationalization of the application from a technical point of view,
> security audit, UI design...). However I don't want to "steal" work forces
> from the rest of the Mageia project. There's no urgence right now on
> mageia-app-db side, I think. However, any help is welcome !
> Samuel

For packagekit support, basically, there's a feature matrix that needs to be 

so, a feature should be implemented on both urpmi side and packagekit side
( http://cgit.freedesktop.org/packagekit/tree/backends/urpmi/helpers )

the way i see it we need:
 - DownloadPackages
 - InstallFiles
 - WhatProvides
 - (possibly simulate option)

and these filters:
 - Free
 - Arch

(i don't think all features in the matrix apply, but then i don't know that 
much about it.)

More information about the Mageia-dev mailing list