Maine Linux User Group, Northern Chapter
Slackbuilds
I moved my post from the forum to here, because it turns out it probably should have been put here in the first place. Sorry!
I was installing the Catalyst developer framework in Perl using Local::Lib the other day, and i could not help but notice an annoying sounding warning stating that my version of Perl, 5.10.0, which comes with the Slackware 13.0 GNU/Linux distribution, has the "Unknown error bug". Which makes fuzzy errors or doesn't report anything at all if there is something wrong with your MVC controller code in Catalyst, for example. I chose to install it anyhow and take a look, showing interest in how Catalyst worked and thinking that I could use it, I decided I should install perl 5.10.1,
Perl 5.10.1 fixes the unknown error bug in 5.10.0, so I asked a few questions about upgrading in the #perl channel on freenode. This is where I got an idea: I could write up a SlackBuilds script, and make a distribution package for slackware 13.0 that would fix this.
SlackBuild scripts are Slackware's version of the FreeBSD Ports collection, only not so official. However, instead of just navigating to /usr/ports and entering in make and sudo make install to download, compile, and install a package to your system, you first download and extract the slackbuild, move or copy the sources of the application you are building to the slackbuild directory which was extracted, and execute the slackbuild as a shell script. the end result: usualy a slackware package found in /tmp. i think this is really neat.
To build my own slackbuild I found documentation on slackwiki, and on the slackbuilds.org website. The building of my slackbuild was quite fun and exciting, I would have to recompile a few times to see if the script worked properly, sometimes failing on the package creation at the end of it all with unexpected end of file (Eventually fixed). Uploading my slackbuild was fairly simple except I found that the x86_64 entries in the .info file are required even if they are empty strings. I even talked with the folks in #slackbuilds on freenode, even though it was a package already included in Slackware, they said it is worth a try, because it may be helpful for others, and the admins might make an exception.
I was really happy I was able to make something work so well, perl installed nicely from the package and was compiled the way the folks on #perl recommended.
I will from to on unless said otherwise in the future be posting my slackbuilds on my website at:
http://brianhodgins.com/files/slackbuilds/
There, the perl slackbuild and built package is stored.
I was installing the Catalyst developer framework in Perl using Local::Lib the other day, and i could not help but notice an annoying sounding warning stating that my version of Perl, 5.10.0, which comes with the Slackware 13.0 GNU/Linux distribution, has the "Unknown error bug". Which makes fuzzy errors or doesn't report anything at all if there is something wrong with your MVC controller code in Catalyst, for example. I chose to install it anyhow and take a look, showing interest in how Catalyst worked and thinking that I could use it, I decided I should install perl 5.10.1,
Perl 5.10.1 fixes the unknown error bug in 5.10.0, so I asked a few questions about upgrading in the #perl channel on freenode. This is where I got an idea: I could write up a SlackBuilds script, and make a distribution package for slackware 13.0 that would fix this.
SlackBuild scripts are Slackware's version of the FreeBSD Ports collection, only not so official. However, instead of just navigating to /usr/ports and entering in make and sudo make install to download, compile, and install a package to your system, you first download and extract the slackbuild, move or copy the sources of the application you are building to the slackbuild directory which was extracted, and execute the slackbuild as a shell script. the end result: usualy a slackware package found in /tmp. i think this is really neat.
To build my own slackbuild I found documentation on slackwiki, and on the slackbuilds.org website. The building of my slackbuild was quite fun and exciting, I would have to recompile a few times to see if the script worked properly, sometimes failing on the package creation at the end of it all with unexpected end of file (Eventually fixed). Uploading my slackbuild was fairly simple except I found that the x86_64 entries in the .info file are required even if they are empty strings. I even talked with the folks in #slackbuilds on freenode, even though it was a package already included in Slackware, they said it is worth a try, because it may be helpful for others, and the admins might make an exception.
I was really happy I was able to make something work so well, perl installed nicely from the package and was compiled the way the folks on #perl recommended.
I will from to on unless said otherwise in the future be posting my slackbuilds on my website at:
http://brianhodgins.com/files/slackbuilds/
There, the perl slackbuild and built package is stored.
Tags: slackbuilds
Add a Comment
About
Badge
© 2009 Created by Seth W. Klein on Ning. Create a Ning Network!
You need to be a member of MELUG North to add comments!
Join this Ning Network