| Summary: | Please create a PackageKit project | ||
|---|---|---|---|
| Product: | freedesktop.org | Reporter: | Richard Hughes <richard> |
| Component: | Project Creation Requests | Assignee: | fd.o Admin Massive <sitewranglers> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | ken.vandine, thelema314 |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
Sorry to ping, but I've got about 4 or 5 contributors now that I would just like to be able to say to "please push" rather than applying all the patches myself. I'm also in desparate need of a maling list. Thanks! The existing repo is at git://people.freedesktop.org/~hughsient/PackageKit Many thanks. git and list created: ssh://git.freedesktop.org/git/packagekit packagekit@lists.freedesktop.org sorry it's taken so long, this conference has swallowed my life. Thanks Daniel, I've updated all the links on the project page. I owe you a beer. :-) no problem. let me know if you need anything else (e.g. packagekit.fd.o web space, etc). packagekit.fd.o would be great, yes please. I've been using live.gnome.org but that is non-ideal for obvious reasons. Also, could commit messages be sent to the mailing list please? Thanks. Ohh, and a bugzilla component would be lovely pls. beer++. all done. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Description PackageKit is a dbus abstraction layer that allows the session user to do cool stuff rather that worry about the underlying software package install system. Scope Initially providing: * an update session daemon to notify of state and current task * a system daemon (started with system activation) that talks to a backend * an application chooser that lets a user search and install GUI applications * a backend to interface with a fictional packaging system * a DBUS api for session and system programs to use Design constraints: * Only one backend can be compiled in, yum, apt, emerge cannot be selected at runtime. * Written in C. * Uses system activation to only be executed when required. * Using a "thick" backend design to abstract efficiently the different packaging systems. See http://hughsient.livejournal.com/ for more information. I've had amazing support from the community, and have been asked to host the code on fd.o. I've already got commit on hal, ohm and hal-info, and my username is hughsient. Many thanks.