It took me a while to get everything work on my Fedora Core 3 box. I needed to use some tricks to make it install. So I decided to share my experience with FC3 users.

1. Install libstatgrab as usual:

2. My tricks:
- copy the package information file (libstatgrab.ps) from the folder it is placed by default (/usr/local/lib/pkgconfig) to /usr/lib/pkgconfig:

- make a symbolic link to the library:

3. And now you can install pystatgrab by the command


PS. Does anybody know where I can find description of all functions of libstatgrab?

Well, not every user can predict that it is needed to be done like this. I made default installation w/o specifying the prefix. So I didn't want to go through all the folders, delete all installed files and then install it again to another directory.

So this detour worked for me fine and I'm not claiming that this is the only way to install the lib :) Just one option.

Sylvain, you might want to add things like this to the adesklet README, and on the main site somewhere. Like jeepston says, not every user knows about it. Why not give em a heads up? ;)

I understand that, but seeing as how I see an increasing number of desklets using libstatgrab/pystatgrab, its more than just an individual desklet's problem. If a user has problems with a certain subgroup of desklets (e.g., system monitors), while the problem doesn't lie within the interpreter itself, it is still an adesklet problem as it can possibly affect users' experiences of adesklets itself. I agree it's more of an image problem than anything...but why alienate a group of users (Fedora users using libstatgrab) by shrugging them off onto someone else? I don't think its a problem as of yet, and I agree that you can't test all configurations of every aspect of the installation process or of every dependancy of every desklet...when it's a commonly used tool of many desklets, I would submit that it IS a issue that concerns the project as a whole.



While I agree with this (yes people RTFM), there are plenty of ahem...users who don't know this and wouldn't know it was the problem if it wasn't spelled out. Again, I'm not saying that you should explain the whole process step-by-step (Chapter 1: Powering up your System), but when you have a wide audience, you should take in to account those users that don't have as much experience as you would like. I would be disdainful of a project that simply demanded every user know every part of every system and eschewed the problems of 'normal' users that couldn't necessarily code whatever desklet they want. I'm not saying that I'm getting this impression, but it's such a simple thing to add a small line into a README or FAQ as a heads-up (Hey Fedora users, you might want to do this to install libstatgrab if you need it, since many desklets require it.).