Living the Slackware 13.37.life, and LOVING IT!
Posted 09-08-2011 at 07:18 PM by Z_Tagr
Thursday, Sept. 8th, 2011
I have been learning the "ropes" of Linux AND Slackware now since around the first of July, and am coming along quite well, I think!
I have been studying many different kinds of bash scripts, leaning heavily towards the "Slackbuild" scripts, as I was a tad familiar with the:
"./configure --prefix=/usr", "make" and "make install"
type of syntax from some experience with several types of GNU software on my MSDOS systems in the past. I used DJGPP (the GNU-C/C++ compiler for MSDOS), and built MAME for the PC using that compiler, as well as several other bits of development work I did on my own (I even wrote a "Game-Of-LIFE" version using DJGPP and the GLIB library at one point!).
I liked the simplicity of the 32-bit "flat-model" that, at the time, required software such as the Phar-Lap DOS-Extender to get when using the MS Visual C++ compiler for 32-bit MSDOS-based applications...
And, just learning a lot about the various command-line commands has kept me fairly busy for the last little while. But now I'm starting to "chomp at the bit" getting ready to begin some "real" Linux development work!
I think I might start with something like a simple "utility"-like app. or something to flex my wings. I just need to find a few good packages of source that are fairly well commented, and I have to set up a development environment. All these things take time, I know, but I am ANTSY!!!
Lately, I have been installing some of the "larger" multimedia apps. like LIVES
and Rosegarden, which had a lot of dependencies to acquire and install. This was all mostly for practice at TROUBLESHOOTING these processes, because even Slackbuilds packages have some "quirks"! You must have had situations where, when you go to run the Slackbuild script, and the first message you get is that the
SOURCE PACKAGE FILE is "missing" (even though you downloaded it from Slackbuilds, and you KNOW that you placed it in the "build" dir.! Then, you look at the NAME of the source package, and it's something like "anypackage.tar.tar", when the SlackBuild script is expecting "anypackage.tar.gz"...; you just need to RENAME the source package (at least, in every situation I've encountered so far!).
I have learned a lot from the Slackbuild scripts, and always enjoy looking them over before I build / install a package!
Well, thats all for today!
I have been learning the "ropes" of Linux AND Slackware now since around the first of July, and am coming along quite well, I think!
I have been studying many different kinds of bash scripts, leaning heavily towards the "Slackbuild" scripts, as I was a tad familiar with the:
"./configure --prefix=/usr", "make" and "make install"
type of syntax from some experience with several types of GNU software on my MSDOS systems in the past. I used DJGPP (the GNU-C/C++ compiler for MSDOS), and built MAME for the PC using that compiler, as well as several other bits of development work I did on my own (I even wrote a "Game-Of-LIFE" version using DJGPP and the GLIB library at one point!).
I liked the simplicity of the 32-bit "flat-model" that, at the time, required software such as the Phar-Lap DOS-Extender to get when using the MS Visual C++ compiler for 32-bit MSDOS-based applications...
And, just learning a lot about the various command-line commands has kept me fairly busy for the last little while. But now I'm starting to "chomp at the bit" getting ready to begin some "real" Linux development work!
I think I might start with something like a simple "utility"-like app. or something to flex my wings. I just need to find a few good packages of source that are fairly well commented, and I have to set up a development environment. All these things take time, I know, but I am ANTSY!!!
Lately, I have been installing some of the "larger" multimedia apps. like LIVES
and Rosegarden, which had a lot of dependencies to acquire and install. This was all mostly for practice at TROUBLESHOOTING these processes, because even Slackbuilds packages have some "quirks"! You must have had situations where, when you go to run the Slackbuild script, and the first message you get is that the
SOURCE PACKAGE FILE is "missing" (even though you downloaded it from Slackbuilds, and you KNOW that you placed it in the "build" dir.! Then, you look at the NAME of the source package, and it's something like "anypackage.tar.tar", when the SlackBuild script is expecting "anypackage.tar.gz"...; you just need to RENAME the source package (at least, in every situation I've encountered so far!).
I have learned a lot from the Slackbuild scripts, and always enjoy looking them over before I build / install a package!
Well, thats all for today!
Total Comments 3
Comments
-
I've never encountered the tar.tar problem but you should eventually submit a slackbuild just to see how that process works.
As for a utility that you could write, try finding an existing project whose development may have stalled, learning the code base and reviving it. There's no need to reinvent the wheel on some projects if you know what I mean.Posted 09-10-2011 at 07:45 AM by Ian John Locke II 
-
Souds like you're having way too much fun! Kudos!
The Linux Jargon is a little above my level, but I sure hope to re-read your entries when I catch-up.Posted 09-11-2011 at 08:07 AM by m3rl1n
-
I gotta agree with Ian's comment, one of the best ways of writing a utility is to pick up something someone else couldn't finished and rewrite it (or write it from scratch in a different language) but still to take all of their ideas and advancements. And of course say "Based on work by SoAndSo."
Posted 09-11-2011 at 01:38 PM by cellarweasel
