Hi all,

Well since I lost my power supply the other day, I had to reload the pc as I needed so many new parts, and decided to do a reinstall of Slack 10.2 as I believed I may have had a broken compiler and thus couldn't do "makepkg" for anything.

My pc: fresh install slack 10.2 full; and I chose menu and checked everything so that it would be installed. Using stock 2.4 kernel and vesa frame buffer. I dont even have a mouse wheel! This is how 'virgin' the install of the pc is. No updates, and no internet, no wire pluged in.

Now I made an 'image' of the slackware partition so I can allways go back.

Now here is a perfect example of the 'h - e - double toothepicks" that I run into with slackware:

For example, I tried to put the latest Amarok on here, version 1.0.4a

Pre-requisites: libmusicbrainz & libtunepimp
There are others, but they are either already in Slackware 10.2 or I simply don't need them. I don't even need k3b plugin. Remember I dont have k3b on here.

1. download libmusicbrainz to my user/home directory for the user account I run as. do 'configure' and I get errors. the errors don't really matter for me to post. I talk about this later.
2. make...get errors.
3. decide not to install it delete the folder.

Now I su to root...and run configure, make and 'makepkg' I chose to reset the symlinks and change the folder permissions as slack's makepkg recommends. I then 'installpkg' I had no errors on config and make.

Now I go to libtunepimp...and configure doesnt' even see the libmusicbrainz!

So I remove the libmusicbrainz from pkgtool...delete my folder for libmusicbrainz and run as root all over again, confi, make and make install this time...no makepkg. goes in fine.

Then I run libtunepimp configure, make, make install and fine.

So my question is:

1. Why is it that the example programs above, like many, many other app's require root to configure, make and make install.

I see everyone say "put the download in your home, config and make as normal then make install as root"

This simply does not work for me. From what I see these config and make's need to see or access files that only the root can get to. And if so, how the heck do you know that they need to? Because many times these app's will go in, you think they are installed but they are not.

Another program I have this issue on: berkely, openldap, hp printing, guarddog.

Now I'm using slack packs from Alien Bob to whom I am so gratefull. But I'd really like to be a 'big boy' and make my own, for learning purposes, and that on some things I can stay a little more current where it matters.

Am I going wrong at the removing symlinks like 'makepkg' recommends, or am I going wrong when 'makepkg' wants me to reset the folder rules?

I thought I had a broken compiler, it must be that I have a broken brain or something

Thanks in advance.

Fogie.

99.9 % of times you really don't need to build sources as root.
Direct installation of software with make install is not recommended because you lose all features of package management, like installation records and possibility of clean uninstalls. For packaging purposes it's much better to install not in root(/) but indirectly into dedicated subdirectory and there after some tweaking like permissions setting and binaries stripping build a new package. Redirection possibilities could be figured out from Makefiles. When created by automake it's DESTDIR variable most of times.
For illustration it's best to see some SlackBuild scripts like following from Slackware-current: libmusicbrainz.SlackBuild

I happen to have a libmusicbrainz package "hidden" in my zinf package directory, so I grabbed the tarball and unpacked it as myself (non-root) and ran configure and make..... no errors whatsoever.
Could it be that you already ran these commands as root (or unpacked the sources being root) before you tried the configure and make commands as your own account?
The default in Pat's and my own packages is to run makepkg "--linkadd y --chown n" i.e. to remove symlinks from the package and add them to the doinst.sh script, and to leave the file ownership alone.

Me, I do not see a problem in being root when building software. Then again, I build my packages in a protected environment (using a QEMU virtual machine) so that no accidental harm comes to my real computers. I do see the point of others that do not want to be root when compiling programs - you never know what might happen, if the makefiles are broken you could accidentally be running "rm-rf"...

Eric

While I have done that in the past and then realized that was bad after our discussion on NFS and folder permissions, I don't think I did it this time. I'm trying to break that habbit. I'll try it again.

Let me see if I have this right then:
-download the file as normal user and save it to my home.
-go to my home, right click on it and choose extract here with 'ark'
-now go into that folder and simply hit F4 key in konqueror, open's up my terminal, I'm still normal user.
-type 'configure'
-type 'make'
-now 'su -'
-enter root pass
-as root I now cd to /home/fogie/libmusicbrainzXX/
-then type makepkg libmusicbrainz.tgz --linkadd y --chown n
-then installpkg libmusicbrainz.tgz

Now I should be good to go right?

You have some good advice here and I don't have anything to add to it except that when I had similar questions I got a lot of help in this thread:

http://www.linuxquestions.org/questi...=1#post2118552

There's your problem. 'makepkg' isn't 'checkinstall'...

manpages aren't being compressed and binaries and libs aren't being stripped but that's the general proceedure for building packages.

If I understood right, you were making a package out of your entire source directory... ;-)

OK I went to slacky.it and grabbed the checkinstall there that Randux linked me to (thanks Randux) and installed it.

-----------------------

You were a "normal user" for the make.....correct? I did this as normal user and it seemed to go fine for me.

But I typed [QUOTE]cat << EOF > install/slack-desc[/quote] and I get nothing. So I guess that meant for me to switch up to root, then cd to the /tmp/pakcage-libmusicbrainz diretory and then call the But when I do that as root, I just get:

I don't get any of this here tho, (should I be typing something else?):

------------------------

Compressing the manpages I guess is ok for me, most of my pc's have plenty of hard drive size. What would an advantage be of "compressing binaries and libs"


I was simply working out of my user account's home directory:

that is : I read somewhere you're supposed to have a 'sandbox' for normal users to play with and compile things if need be, so I just call mine "scratchpad" instead of "sandbox".

Thanks for helping me, I really appreciate it.

That bit of was not meant to run just like that. This command is the start of a so-called "here-document" (look it up like here: http://www.faqs.org/docs/abs/HTML/here-docs.html) which means that all of the text that follows that command line - up to the line starting with the word EOF is part of the command.
The result would be that this text would be written to the file "install/slack-desc".

As to zipping man pages and stripping binaries/libraries, this is of course not needed if you build packages that just you are going to use on your own giant hard disk. But if you intend to distribute your package to other people, you don't know how diskspace starved these computers are going to be. It is simply being nice to those folks if you try to keep your packages as small as possible.

Cheers, Eric

thanks for explaining that Eric. I went to linuxpackages, and saw that they have a tool to make one of these "slack-desc" files, so I made one there and just made a text file and pasted the info and called the file 'slack-desc.txt' and put it in the /tmp/install of the package.

I think I have libtunepimp in right, and libmusic brains.

I ran the .configure on the amarok, but I get an error/warning that KDE is in /opt/kde and that I'm supposed to update KDE with some setting and then restart KDE. Something with KDEDIRRS=/usr;/opt/KDE or something like that I just lost the terminal window darn.

Would this amarok program be an example of when I need to go into their 'configure' script and manually change their script? Or pass an argument when I do the configure? If so what argument would I pass to tell it that KDE is installed on my system in /opt/KDE?

oh I think I have to change prefix=/usr to prefix=/opt/KDE ?

If you really want to do it as generic as possible when you prepare a KDE package, set the prefix like this:
instead of "./configure --prefix=/opt/kde".

By the way, the slack-desc file in your package's "install" directory should be called "slack-desc" not "slack-desc.txt"!

Eric

OK

thanks

You can use checkinstall if you want. All you have to do there is:

./configure --prefix=/blah
make
checkinstall

I highly suggest you eventually move to makepkg at some point. Checkinstall used to be severley bugged when it wrote it's doinst.sh but from what I hear, it doesn't do it anymore. I'm not entirely sure it compresses the man/info pages, strips libs and binaries and if there are any commands that need to be run on the doinst.sh, it won't pick those up either (which results in an incomplete/broken package install). IMO, checkinstall is a pretty weak way to go. There is no substitute for 'makepkg' and personal attention to details.

I always build/run as root. Not the smartest of ideas at times due to carelessness on my part, but I do it none the less. You have the right of it with doing the configure/make as a user and the 'su'ing to root for the 'make install DESTDIR=/tmp/packagename'

As for the 'cat' part, Eric already explained that. All the way down to 'EOF' was meant to be one command. That's kinda why I put spaces above and below it; to seperate it. So you would have copy/pasted all of this:

You compress manpages and strip binaries and libs of their debugging symbols. Your average user doesn't want to debug a program, just run it. It reduces the size of the binaries/libs and is considered 'proper' form for slak-paks... Same thing goes with using a prefix of /usr/local... Don't do it. Not if your going to distribute your package anyway... If manpages get installed to /usr/share/man then move them to /usr/man... If doc's get installed to /usr/share/doc move them to /usr/doc... If you get a /usr/info/dir file and it doesn't come from the texinfo package, then delete it... There are quite a few things to watch out for if you are the anal type and want your packages to be 'proper'. IMO, it's a good idea to just start doing it, else you form bad habits...

Again, good idea. I can't tell you how many times I've screwed stuff up by running as root 24/7.... I'm not worried about attacks from the web, just inadvertent attacks from my own stupidity. I have ZERO apps listening on ports, run a strong iptable firewall script and am behind a router to boot.

I've recursively erased my windows partition a few times because it was mounted. I've wiped /var/log/packages clean once over a typo and numerous other stupid things... But hey... It's a great way to learn... Doesn't happen so often now except when I'm tired.

Anywho, don't forsake 'makepkg' just yet. Study build scripts in the Slackware FTP site and you'll start to understand rather quickly how things work.

Hi Jong

I must have mis-understood you when you said:

As I thought you meant I should get it. I did download it and put it in, but I've been using the process you showed there; so effectively I guess I'm not using it then.

All of my packages have no description, I'm going to have to read Eric's link he gave me there more I guess as creating that text file doesn't seem to work. Baby steps, baby steps

I see over at the how-to at linuxpackages the writer reccommends this for about 90% of the time he says:

Maybe I should do that allways to play it safe, unless I know that it's a KDE required program and then use what Eric gave there.

I noticed as I just tried to do the touchpad driver, even tho the package goes in, I have to copy over to my /usr/lib/modules.... these two files for the touchpad. Maybe when I get more advanced I'll learn how to input that into my script.

Hey Fogie, you mentioned using the slack-desc builder from linuxpackages.net. I just wanted to say this was a great resource for me when learning to create slack-packages the "right way"; this link in particular.

I had this problem too when I first started doing it. It can be a bit touchy at times so here are some tips that got it working right for me.
a) enter in the program name exactly as the base name of your package will appear (case sensitive)

b) same goes for the version #

c) the name of your package must be in this exact format or you will get no description form the slack-desc:
<name from a>-<version from b>-<architecture>-<build number>.tgz
example: seamonkey-1.0.1-i686-1.tgz

I usually just put "noarch" for architecture but you can put in your processor type if you want: ie i686 for me.

have fun making packages!
...drkstr

PS:
I love the slackware package maker. After I learned how to do it, I got a little caried away and tired to turn everything I had the source to, into a package. I even made a package that restores my system and installs all my newly created packages after a clean install of Slack (doinst.sh rocks the house). What fun!