Hi and good morning all.

Now, trickykid lately posted a nice Howto, concerning compilation of sources from the net (see here). Like it is to be expected from a venerable moderator it worked perfectly when I tried it out.

But: as I learned the hard way, it presupposes some knowledge I don't (yet) have, or it doesn't change a thing on the computer. More specific: I downloaded K3b-0.8 and used the instructions provided by trickykid and others. Worked perfectly.

Only KDE still used my old K3b-0.7, which means that make install does not install the thing into KDE at all.

Then I found out with help from LQ, that I had to install it myself into the rpm database. Okay: rpm -Uv K3b-0.8 -- and I get the friendly information, that I am trying to install something other than a package -> forbidden. So here are my questions:

1. Am I guessing correctly, that I have to build a package myself (with rpm, or are there easier ways?)?.

2. Do the makers of K3b really provide easy to use ./configure make make install scripts, without an option to finish work, or are there in fact more commands?

3. What did the make install truly do, then?

4. Since (nearly?) every distribution builds on packages, how can it happen, that only I ran into this problem (I gave up two earlier tries with SuSE 6.4), i.e. why is this never mentioned or rather what (possibly and what else) did I overlook??

I feel definitely, that there is a substantial gap in my knowledge which I'd like to close, but I don't know where to look. Anybody any suggestions? Thanks and bye.

you only install into the rpm db if you are using an rpm, which you aren't. you are using a source install (./configure etc.. yeah?) rpm is a completely different system.

there are rpm's avaiable sure, http://rpmfind.net then "man rpm" for info.

make install copies the compiled files into their final location

SuSE uses rpm -> K3b-0.7 is there. I uninstalled it manually but I still could not insert the newly compiled program. If you say a source-install is "completely different" I must somehow get the two synchronized!?

If make install copies files that's fine, but it does not truly install, since the program is not readily accessible. So what's the "install" part?

When I get rpms from the net -- okay, what are the source-installs for, if one cant get them working? Meaning, there must be a way, mustn't it...

how did you uninstall it manually? just delete the executable? if you ran make install then it will have copied the execuitables to wherever and k3b should run just fine, there is nothing more to do. not usre what you're trying to insert it into. tar.gz (source) is nothing to do with RPM, they are completely different ways of installing programs. but once installed they behave the same way, i.e. it runs.

Hello there Ok, I don't know if this will really help but it's worth a try. In your home directory, delete the .k3b directory and then run K3B again. This time the new(0.8) K3B should load. Hope this helps!

Nono. What I meant was rpm -e. I also uninstalled it with YAST2. I know that deleting the executable is not the way.

It "installs" somewhere below the source-directory. Maybe that is wrong! Do I have to specify for make install the final place for the executable, i.e. do I have to edit it??

As to your last sentence: "but once installed they behave the same way, i.e. it runs." No, regrettably they don't, at least not on my machine.

How are you trying to run it? through a menu option (i.e. the kde K menu of the gnome foot menu?). If so then it could just be that that application launcher is incorrect (and still pointing to the old executable). Unfortunately few programs that you compile from source create entries in the 'start' menus. If you go to a command line, and use tab completion then you can see that way if it is installed. Type the first letter, jab tab. It will either beep at you (so double tap tab to get a list of completions) or will complete/partially complete the command. If it doesn't give you the program you want then continue to type stuff in and jab the tab key. If it isn't there once you've finished then you'll have to search for the thing.

I can never remember how to use the find program so either look under the man page for it or use the locate command. You will probably need to update the locate command's database first by typing as root
There'll be a whole lot of hard drive crunching and it will go on for a while but once its finished just type the name of the program after locate and it should display a list of places which have that name in it.
If it finds it then you may need to type the full path to the program such as /usr/local/bin/k3b to get it to work. It depends how your system is set up and where its been installed to.

Alex

@wonderpun (post #5): I'm doing all this as root (okok security, but I want to make sure, that I don't run into problems dues to wrongly set permissions). /root has no .k3b, neither the users, I just checked !?! Thanks anyhow.

@webtoe (post #7): k3<TAB> just says k3b, no paths no double entries for differing paths. BUT WITH PATH IT WORKS!

Hah, great. Now I just have to find the place in KDE where I can adjust the path for the menu.

Anybody knows whether theres another trick necessary with the language module for K3b (k3b-0.8-i18n) and or the icons?

huh? you mean how to get them working?
I don't know anything really about changing the language in KDE but there should be a setting in the control panel for internationalisation and I'm assuming that kde is smart enough to use that to use the correct files in the internationalisation package (I could be visciously wrong here, this is a wild guess).

Glad I could help

Alex

P.S. once you press tab and it says k3b, press enter and does it work?

No it hasn't got anything to do with KDE-language support. The K3b-team did their language support (?) in an extra resource, called K3b-0.8-i18n (whatever that stands for), which has to be compiled separately (which I did).

As to your PS: No, it just says K3b and starts the old version. The new version is not known. Once I type /root/install/K3b/k3b-0-8/src/k3b (where the new program resides) I get it started. By the way, clicking in Konqueror or cd-ing to /root/install/K3b/k3b-0-8/src and typing k3b does not do the trick, since K3b's menus are then crippled, don't ask me why.

Anyhow: With your help I got it licked. I just have to find where I can adjust the path for the menu in KDE to get the new K3b started, then everything is as I wanted it to. Thanks a lot.

"cd-ing to /root/install/K3b/k3b-0-8/src and typing k3b does not do the trick"

because it till not be on your path and will use libraries from the current installed version

Okay. Is it enough to change $PATH to get it started correctly with the correct libraries, or is there another trick still?

hmmm, just a suggestion but you may need to become root, then shift the K3b directory to somewhere in your path such as /usr/local/.

But altering your path would be necessary anyway its just that its not normal, I don't think, to have programs installed in root's home directory.

Alex

Try this, it works for me ;-)

rpm -e k3b

./configure --prefix=/opt/kde3
make
su
make install

k3b

Since you install this k3b from source it won't appear in rpm database :-(


Have fun :-)

Thank you for your suggestions and help, everybody.