Ever get your girl mad at you? Want to get her unmad long enough to work things out? Got some spare cash?
BUY SOME FLOWERS!
Guaranteed to work.
Ever get your girl mad at you? Want to get her unmad long enough to work things out? Got some spare cash?
BUY SOME FLOWERS!
Guaranteed to work.
Updated uber-patch. I'll be splitting parts of this patch up that are separate from plugins
Download plugin uber-patch
I got it to work! It's just a proof of concept right now, and I'll clean it up later.
The patch does several things that are needed:
So today is my last day in Canada until I decide to visit again. I'll definely be missing my baby girl :(. Hopefully next time I enter won't be as difficult as this month. Thank you Windsor for letting me in, unlike your co-workers in Sarnia!
On a side note, I'm using Windows Live Writer to write this. Seems like a very nice program to write blog posts.
Attached is a python script that can download and save all the chapters from a given fanfiction.net story, stripping out the header and footer.
It requires: python 2.5+, pygtk, and libxml2dom (and all dependencies of the said scripts).
Download fanficgrabber. Extract the zip, and execute the python script once acquiring all dependencies
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?
My newest project is a YaST Policy Editor module. It's much less ambitious than previous failed projects, and will be quite useful, especially as more software becomes PolicyKit enabled (including hopefully YaST itself: http://lists.opensuse.org/yast-devel/2007-10/msg00024.html)
I added mugshot to my OBS repo: http://download.opensuse.org/repositories/home:/jhaygood/openSUSE_10.3/
For more information on mugshot: http://www.mugshot.org
Any other cool packages I should add?
It's available in my home repo: http://download.opensuse.org/repositories/home:/jhaygood/openSUSE_10.3/
Current Version: FileZilla 3.0.1
Architectures: i586, x86_64
OpenSUSE Versions: openSUSE 10.3 (due to dependency on wxGTK 2.8.4)