I need kaffeine-xbu. The package was present in /home:/Max1, now the repo is empty, I assume for ever. I fear I will need to compile kaffeine-xbu for opensuse and after that package it!
Where can I get the informations about how to do this work?
thanks!
Why?
AFAICS kaffeine-xbu is part of the standard “kaffeine” package:
# rpm -ql kaffeine
/usr/bin/kaffeine
/usr/bin/kaffeine-xbu
...
Or do you mean something else?
hi wolfi,
well, it is a bit complicated.
- I use a Sundtek dvbs card whose drivers are not “orthodox”. There is no problem with kde3-kaffeine, but kaffeine 4 is simplified and needs to be patched to became able to find the drivers. For what I know there is no problem by other distributions. Somebody was offering a “suse working” kaffeine in the mentioned repo. Sundtek let me understand that they do not have a replacement.
- Conclusion: maybe is time for me to stop just writing gambas applets and do some little work.
You can still use kde3-kaffeine.
It is available from Packman, and even included in the standard distribution.
I doubt though that kaffeine 4 is any different in other distributions.
- Conclusion: maybe is time for me to stop just writing gambas applets and do some little work.
Create an account on OBS, branch the package and add the necessary patch.
It’s not really hard… 
You could even submit the changed package back then to the official repo to have this fixed for everybody (KDE:Extra is the development project for Factory).
If you can point me to the patch I can create a package for you.
sorry for the delay, I got a visit and the guest remained for dinner.
wolfi, I understand your doubt. I also agree that playing Hexen is more pleasant as:
#include <sys/stat.h>
#include <dirent.h>
#include <sys/inotify.h>
#include <vector>
#include <stdlib.h>
#include <unistd.h>
#include “…/log.h”
#include “dvbtransponder.h”
well, I am using right now such a kaffeine despite missing the last version and I didn’t download the source: now it is too late. kde3-kaffeine would be preferable for many reasons but I hate double clicking. I think I would be able to find the right lines in the code and displace them under mouse_click or similar. similar means mouse_up or mouse_down. .) the problem is the same: I need informations about setting up a suse for compiling kaffeine and I need informations about packaging. can somebody here provide me with links containing such informations or should I ask Mr Snowen in Russia?!
???
Where do you have to double-click in kde3-kaffeine?
Also, it should just follow the KDE3 configuration, so maybe you just should set single-click in there (kcontrol), although that actually should be the default.
Anyway, I found a patch and am going to create a package for you…
As I said, doing so is quite easy on OBS. Just branch the package and add the patch.
And then maybe submit back the package to the project where you took it from in the first place.
The package is ready:
https://build.opensuse.org/package/show/home:wolfi323:branches:KDE:Extra/kaffeine
You can have a look at how a package is created there (in essence you need a .spec file which tells OBS or rpmbuild how to create the RPM)
Click on the “Download package” link to download/install the RPM.
I hope it works!
I can’t believe it.
sure, it works, but for me it looks like an unknown branch of magic.
-
your first answer was showing a quite dogmatic personality. suddenly you have the work done, in your repo I see the sundtek patch which I didn’t mention, you must have understood my problem despite the very partial exposition because the right package is there. finally the whole procedure, code hunting included, seams to take minutes what on my eyes looks also impossible.
-
I had already the patch, but I used something like this just to recompile vmware modules. so, I was asking myself about the source to patch. the first impression was telling me that the patch is very heavy and I was thinking about inserting manually all that additions, possibly in the last kaffeine version.8
-
I don’t want to abuse your patience, on the other hand I really would like to learn what you did. a propos of stressing your patience, could you make also the kde3-single click-kaffeine? to select senders in the list box they need to be double clicked despite the single click event looks empty. I think there are no configuration possibilities, I installed the whole kde3 and I think to have checked everything.
-
do I need a second suse with all possible devel packages inside?
thanks for your kindness, but even more for your knowledge!
Well, I didn’t know what you mean exactly at first. (you were asking about “kaffeine-xbu”)
Then I googled for this, and found the patch in Ubuntu’s kaffeine package.
OTOH, I also remember reading something about this patch in the Kaffeine forums.
- I had already the patch, but I used something like this just to recompile vmware modules. so, I was asking myself about the source to patch. the first impression was telling me that the patch is very heavy and I was thinking about inserting manually all that additions, possibly in the last kaffeine version.8
You can get the source code from the Kaffeine homepage. Then apply the patch (with the command “patch”) and compile it.
Or just use openSUSE’s kaffeine package as starting point (as I already suggested, and did myself). This includes some other patches already.
Have a look at the package’s spec file for how to compile it. (you can view/download files on OBS’s web interface f.e.)
You can install the package’s source code with “zypper si kaffeine” (si=source-install). You then find all the files below ~/rpmbuild (or /usr/src/packages/ if you did it as root). Rebuild the package after you made your changes with “rpmbuild -bb ~/rpmbuild/SPECS/kaffeine.spec” or similar, the packages will then be created in ~/rpmbuild/RPMS/.
- I don’t want to abuse your patience, on the other hand I really would like to learn what you did.
I just did what I proposed before: I branched the kaffeine package from KDE:Extra and added the patch.
If you want to see all changes I did, click on “Has a link diff” just above “Download package”.
The added entry in kaffeine.changes is mainly for documentation purposes.
So in the end, I just had to add two lines in the spec file (one to specify the patch file, and one to apply it), and upload the patch.
To “branch” a package isn’t exactly difficult either. Just search for the package you want to branch, and click on “Branch package”… (you have to be logged in for that of course). You then have a “copy” (well not exactly, it is a link so whenever the original package gets changed, you get the changes as well) of that package in your home repo and can change it as you please.
a propos of stressing your patience, could you make also the kde3-single click-kaffeine?
I don’t understand that.
There is no “kde3-single click-kaffeine” AFAIK. And I cannot remember having to double-click there, but it has been a while (years) since I last used it, so I’m not really sure now.
to select senders in the list box they need to be double clicked despite the single click event looks empty. I think there are no configuration possibilities, I installed the whole kde3 and I think to have checked everything.
Hm, have you tried the global KDE3 single-click vs. double-click setting? (in kcontrol, as I said)
I don’t have either kde3-kaffeine nor KDE3 installed here at the moment.
- do I need a second suse with all possible devel packages inside?
No, just install those that you need on your existing openSUSE.
The easiest way to do that for Kaffeine would be:
sudo zypper si -d kaffeine
That would install everything that’s needed to build kaffeine.
great, you gave me a complete scheme in a few words. let wait with kde3-kaffeine: for now I have my first exercise, I should do again what you did. with your permission and at least for the moment I would also take the liberty of mentioning the new repo in the sundtek forum for the other suse users.
thanks a lot, you are great!
No problem, but I think I will try to push this into the standard KDE:Extra repo anyway. It would then be part of the standard package for 13.2 as well.
So my branch repo might disappear again in the future…