PackageKit

From openSUSE

(Difference between revisions)
Revision as of 15:23, 8 August 2008
Mvidner (Talk | contribs)
categorized
� Previous diff
Revision as of 09:38, 9 December 2008
Haass (Talk | contribs)

Next diff →
Line 2: Line 2:
(From packagekit.org: ) (From packagekit.org: )
-[http://packagekit.org/ PackageKit] is a D-Bus abstraction layer that allows the session user to manage packages in a secure way using a cross-distro, cross-architecture API. +[http://packagekit.org/ PackageKit] is a D-Bus abstraction layer that allows the session user to manage packages in a secure way using a cross-distro, cross-architecture API.
== Integration with OpenSUSE == == Integration with OpenSUSE ==
-=== Base System Requirements (not met in OpenSUSE 10.3) ===+=== Base System Requirements for Development (openSUSE 11.1) ===
-For now we will not create packages for 10.3 as it would require to replace a lot of software with newer / recompiled versions. You should use Factory for development.+* C/C++ developers enivronment
-* dbus-1 1.1.3 (make sure it's a version newer than August 2007)+* PolicyKit-devel
- Version 1.1.20 is in Factory+
-* PolicyKit 0.7+* dbus-1-devel
- Version 0.7 is in Factory.+
-* [[libzypp]] >= 4.3.2+* dbus-1-glib-devel
- Packages are available here [http://download.opensuse.org/repositories/openSUSE:Factory/standard/]+
-* intltool >= 0.36.3-1+* glib2-devel
- Version 0.37.1 has been submitted to factory.+
-=== Progress ===+* libzypp-devel
-PackageKit and gnome-packagekit Version 0.1.9.1 are submitted to Factory.+* intltool
-Currently the PolicyKit helpers do not have the necessary perms yet. See the PolicyKit changelog to set these.+* gtk-doc
-[https://bugzilla.novell.com/show_bug.cgi?id=295341 Setting the PolicyKit helper perms manually]+
-If you want to build your own version from source -+* sqlite3-devel
- Build the zypp backend+
- Use the zypp backend as default at runtime when not specified+
- We use PolicyKit as the default security framework+
- Tell the install where to find dbus (does not quite work)+
- Optional - turn on debugging and turn of optimization for better results in gdb+
- ./autogen.sh CFLAGS="-g -O0" --with-default-backend=zypp --with-dbus-sys=/etc/dbus-1/system.d --enable-zypp+=== Building ===
-=== Running ===+To configure your build-environment run:
-The dbus activation problems have been solved so the packagekitd daemon will now activate automatically when needed.+ ./autogen.sh
 + --prefix=/usr
 + --libdir=/usr/lib
 + --localstatedir=/var
 + --sysconfigdir=/etc
 + --disable-browser-plugin
 + --disable-qt
 + --disable-gtk-doc
 + --disable-gstreamer-plugin
 + --enable-developer
 + --enable-local
 + --enable-zypp
 + --with-security-framework=polkit
 + --with-default-backend=zypp
 +=== Running and Debuging ===
To test and get debug info from PackageKit with zypp as backend use the script in the src dir To test and get debug info from PackageKit with zypp as backend use the script in the src dir
./run-pk.sh zypp ./run-pk.sh zypp
 +This script simply calls the local built packagekit-daemon with the following parameters:
 + --verbose
 + --disable-timer # PackageKit will not exit after the set timeout
 + --backend=zypp # Set zypp as used backend, otherwise the dummy backend will be started
 +
 +To run the the packagekit-dameon in gdb edit the gdb.sh script and set zypp as backend.
 +
 +=== Configuration Files ===
 +* /etc/PackageKit/PackageKit.conf
 +
 +=== Log-Files ===
 +* /var/log/pk_backend_zypp & /var/log/pk-backend-zypp-1
 + This file includes all log-messages from libzypp
 +*/var/log/PackageKit
 + This file includes all log-messages from the PackageKit daemon (in the standard configuration only the errors)
 +
 +Please attach all of this files when reporting a bug!!!
=== Links === === Links ===
Line 51: Line 72:
[http://www.packagekit.org http://www.packagekit.org] [http://www.packagekit.org http://www.packagekit.org]
-[http://del.icio.us/joshkress/PackageKit http://del.icio.us/joshkress/PackageKit]+Before starting to develop please read: [http://www.packagekit.org/gtk-doc/index.html]
-[http://ken.vandine.org/?p=267 http://ken.vandine.org/?p=267]+Blog of Richard Hughes (the author of PackageKit): [http://blogs.gnome.org/hughsie/]

Revision as of 09:38, 9 December 2008

(From packagekit.org: )

PackageKit is a D-Bus abstraction layer that allows the session user to manage packages in a secure way using a cross-distro, cross-architecture API.

Contents

Integration with OpenSUSE

Base System Requirements for Development (openSUSE 11.1)

  • C/C++ developers enivronment
  • PolicyKit-devel
  • dbus-1-devel
  • dbus-1-glib-devel
  • glib2-devel
  • libzypp-devel
  • intltool
  • gtk-doc
  • sqlite3-devel

Building

To configure your build-environment run:

   ./autogen.sh
     --prefix=/usr
     --libdir=/usr/lib
     --localstatedir=/var
     --sysconfigdir=/etc
     --disable-browser-plugin
     --disable-qt
     --disable-gtk-doc
     --disable-gstreamer-plugin
     --enable-developer
     --enable-local
     --enable-zypp
     --with-security-framework=polkit
     --with-default-backend=zypp

Running and Debuging

To test and get debug info from PackageKit with zypp as backend use the script in the src dir

   ./run-pk.sh zypp

This script simply calls the local built packagekit-daemon with the following parameters:

   --verbose        
   --disable-timer  # PackageKit will not exit after the set timeout
   --backend=zypp   # Set zypp as used backend, otherwise the dummy backend will be started

To run the the packagekit-dameon in gdb edit the gdb.sh script and set zypp as backend.

Configuration Files

  • /etc/PackageKit/PackageKit.conf

Log-Files

  • /var/log/pk_backend_zypp & /var/log/pk-backend-zypp-1
 This file includes all log-messages from libzypp
  • /var/log/PackageKit
This file includes all log-messages from the PackageKit daemon (in the standard configuration only the errors)

Please attach all of this files when reporting a bug!!!

Links

Some links for development:

http://www.packagekit.org

Before starting to develop please read: [1]

Blog of Richard Hughes (the author of PackageKit): [2]