Recently in OpenSUSE Category
libpurple-facebook 1.61 is now available for openSUSE 11.0, 11.1, and Factory in home:jhaygood. For users not on Factory, this will pull in json-glib from home:jhaygood (which is being pulled from GNOME:Factory for now)
I updated my libpurple-facebook package in the build service to 1.61. However, it requires json-glib, which is currently only available in openSUSE Factory at the moment. I'll be trying to figure out how to get it to work on openSUSE 11.1 shortly.
Yay! I also got my openSUSE Lizards account today as well.
There's a much better way to do this now. See my updated post here
I just packaged the pidgin-facebookchat plugin for openSUSE 11.0 and openSUSE 11.1 in my home project in the openSUSE Build Service. The package is called libpurple-facebook to be consistent with other packages.
Enjoy, and please let me know if there are any problems!
What is Geeko Gears? Simple: its a project to redo the build system of Google's open source Gears software.
Initial Goals:
- Use autotools to create the Makefile
- Link to system libraries instead of using internal ones
- Allow to be built for all platforms openSUSE supports (32-bit, 64-bit, PowerPC)
- Remain 100% API compatible with upstream
I got my openSUSE 11 box set today shipped to me! It's the free retail box contributors get.
I just got Twitux packaged for openSUSE 10.3, a twitter client for GNOME
One Click Link: Twitux
jpr noted on his blog that I've been interesting in integrating PackageKit into the distribution. This is one of my many goals for making openSUSE a better operating system than it already is.
Currently, I'm waiting for PolicyKit 0.5 and dbus 1.1.2 to get into the distribution. After that, we can write a zypp backend, test it, and send it upstream to PackageKit, since they want backends to be part of PackageKit themselves. Our various updaters can be replaced by PackageKit frontends, and Benji's One-Click Install can be simplified since it can use PackageKit to set up the repositories and install the packages, instead of a nasty hack of calling another yast module via a longish command.
I'm currently working on the policy-editor module for YaST (to edit
PolicyKit configuration), and I want some input on some of the design
decisions:
1. I'm using python code for the loading and parsing of the policy
description files (its XML, and DOM makes parsing XML a dream). The
policy description files describes the actions, provides a
(translateable) description, and sane defaults.
That part I'm fine with, since I can use YCP to interact with and load
the model from the python code.
2. The actual policies as defined by the system administrator is located
in /etc/PolicyKit/PolicyKit.conf
Now my question is, how should I go about generating this file? Should
we use this file directly, or use sysconfig to generate the file
dynamically, and potentially provide for a "local include" so that you
can include custom policies not set via YaST?
