I'm actually experimenting doing my own packages with slacky.it's build scripts. Until recently, when I needed an extra package, I just compiled the source - and all the needed dependencies - then I installed everything one after another with checkinstall. This gets a bit tedious when I have to do it on many machines, that's why I wanted to experiment with the Slackbuild scripts.
I tried the following.
Create two directories, ~/source and ~/packages. Let's say I want to build lame: I create a directory ~/source/lame, which will contain a) the lame source tarball b) lame.Slackbuild and c) the slack-desc for lame. So far so good. In this directory, I su to root, and then I simple do the following:
Codice: Seleziona tutto
# ./lame.SlackBuildOn my main machine, I have several partitions, with a total of three complete Slackware 10.2 installs. The first Slackware is my "production" environment, the one I write this message on. Only tested software here. Then I have my "build environment". And the 3rd one is the "testing" environment.
Problem: I can build packages and install them OK, it seems, in the build environment. BUT... when I transfer these packages to the testing environment and install them with a simple installpkg, some packages have errors. Example: kaffeine and superkaramba don't appear anymore in the KDE menu, and when I start kaffeine manually, it sort of starts, but with an error messge about a kaffeine_something module not found.
Am I doing wrong in the build process?
Suggestions very welcome,
Niki Kovacs
PS: I understand a little bit italian.... e possibile rispondere in italiano


