Gentoo Archives: gentoo-soc

From: Mounir Lamouri <volkmar@g.o>
To: gentoo-dev@l.g.o
Cc: gentoo-soc@l.g.o, Zac Medico <zmedico@g.o>, dberkholz@g.o
Subject: [gentoo-soc] [gsoc-status] portage backend for PackageKit
Date: Mon, 15 Jun 2009 20:51:59
Message-Id: 4A36B468.7090707@gentoo.org
1 Hi,
2
3 I'm working on a portage backend for PackageKit [1].
4
5 As I did not really present my project, you have to know PackageKit is
6 an universal (distribution-wide) package manager. To do so, every
7 package manager which wants to work with PackageKit have to follow an api.
8
9 PackageKit is compatible with a lot of package managers. Actually, it's
10 the default one in Fedora and some other distributions.
11 The main advantage of using PackageKit is to have a simple application
12 working in most distributions. It will be a great advantage to make
13 Gentoo more user-friendly. With a USE-flag GUI manager, it could be
14 really great.
15
16 The main difficulties for this project is the source-based aspect of
17 Gentoo and the verbosity of portage. I mean even if PackageKit is
18 designed to fit every needs, portage backend is the first source-based
19 distribution backend and we will have to adapt some things. In addition,
20 some information provided by portage like ewarn and elog messages and
21 new configuration files have to be prompted even when using PackageKit.
22
23 So, where are we right now ?
24 The planning says "every basic features should be done June 15th".
25 Actually, I still have to do 2 features : list update candidates and do
26 update. Every other basic features (install, remove, sync, details, dep,
27 reverse-dep, groups, ...) have been done.
28 To my defense, that's three days I'm sick.
29 In addition, as PackageKit refuses interactivity, I've pushed
30 ACCEPT_LICENSE default value to remove interactivity from ebuilds using
31 check_license function from eutils eclass.
32
33 What's going to be done right now ?
34 Repositories management have to be added. With zmedico, we were talking
35 about doing this directly in the portage api. Basically, it will be
36 merging layman into portage. It's not 100% sure right now but probable.
37 Beginning the hard work of messages management and bug fixes.
38
39 I will try, to add needed ebuilds in the tree this week to let people
40 test PackageKit on Gentoo as it will be "usable" even if not recommended
41 yet. That's what we call an alpha version I think ;)
42
43 [1] http://packagekit.org/
44
45 Thanks,
46 Mounir

Replies

Subject Author
Re: [gentoo-soc] [gsoc-status] portage backend for PackageKit Arun Raghavan <arunissatan@×××××.com>
Re: [gentoo-soc] [gsoc-status] portage backend for PackageKit Arne Babenhauserheide <arne_bab@×××.de>