I was actually going to make my own how-to's on package-management and/or package building in Slackware 13.0, but someone beat me to it.., or at least the management-part that is. And I must say, it was an easy, most informative and straightforward read, cudos to the author.
The method(s) described in the how-to is how I've been doing it the later years, only I used 'slapt-get' instead of 'slackpkg' to update and upgrade. But I'm now using 'slackpkg' since it is part of Slackware Linux' original management tools.
I've also made an all-in-one 'automagic' slackbuild shell script I call "buildpkg", which, with a couple of modifications will be able to resolve dependencies, download, compile, package and install.., then build the original package for which the dependency was added for, making the whole process effortless.
The point of the script was to simplify (for me) the quite dubious and lengthy process of watching the compile-process for missing libraries/binaries/etc. when compiling data-intensive applications (like 'ffmpeg' and 'fuppes'), and rather store minor-errors in a logfile to weed out after compilation success. Thus saving me from a lot of blank-faced staring at the compile-output screen, when I really just want an app to compile and work without a lot of additional functionality, and rather just build the app as 'vanilla' as possible.
I mostly use it on media-applications, but I'm progressively modifying it to work on just about anything. In time, maybe it will be used by others. ;-)
Link:
Posts
0 kommentarer :
Post a Comment