Trying out Slackware

[Steve Holmes]

I first use what packages Slackware has available and if I want
something Slack doesn't have available, then I compile from sources
and where possible, I use something like checkinstall to help in
building a slackware compatible package.  One thing I like about
packages - even the ones I build is I can compile something like
mplayer on my fast machine and then just drop in the package on my
slower laptop and just install it.  Another advantage to packages -
once built either by myself or from slackware distro, is it is much
easier to remove all components.  Some tarballs are complex enough
that it is nearly impossible to find all the pieces to be removed.
This is especially important when you want to upgrade.

On Mon, Jun 25, 2007 at 07:41:55AM -0700, Ralph W. Reid wrote:
> Slackware does have fewer 'pre-installed' packages than some other
> distributions, but for some of us, just about everything actually
> needed is there.  On the rare occasion when I have decided to add
> something to my system, I have compiled the new program from the
> original source.  At the moment, the only program I recall installing
> this way was mplayer.  Everything else I needed seems to have already
> been included--I just needed to write an occasional script or small C
> or Ada program to use what was already available on the system.  I did
> compile some adventure games from source some time ago, but whether I
> 'needed' to add those to the system is somewhat debatable ;) .  Your
> requirements may differ from mine--reviewing the distributions to find
> out which one seems to fulfill most of your needs out of the box is a
> good idea.  Don't forget to look through the 'extras' directory in
> your favorite Slackware distribution--you might find a package already
> set up there to handle your requirements.
> 
> As for making packages in Slackware, you can do this if you like so
> that your packages can be installed, updated, or removed with the
> standard Slackware package tools.  You will still have to get the
> source code and compile it to create a complete package to be
> installed with installpkg, or perhaps you could just put your newly
> compiled program in a place like /usr/local/bin without using any of
> the package management tools.
> 
> HTH, and have a great day.
> 
> On Sun, Jun 24, 2007 at 07:43:24PM -0700, Zachary Kline wrote:
> > Hiya,
> >     Since I don't technically have an actual computer running Linux to speak of, in some ways I have an advantage.  I'm able to try out new Linux distributions on the fly and as I become interested in them.  Today I tried out Slackware 11.0, and I really like it so far.  The only thing I have to get used to is the amount that comes preinstalled and the amount that isn't available.  There are far fewer packages in the Slackware repositories than in, say, the Gentoo Portage system or Debian's package databases.  But I don't know if this is a bad thing or not.
> >     That being said, could any of you Slackware veterans give me a tip or two?  What is the method for installing stuff that isn't in the Slackware package lists?  Do you compile from source, or make a Slackware package with makepkg?
> > Thanks,
> > Zack.
> > PS: I love BSD init.
> 
> -- 
> Ralph.  N6BNO.  Wisdom comes from central processing, not from I/O.
> rreid at sunset.net  http://personalweb.sunset.net/~rreid
> ...passing through The City of Internet at the speed of light...
> CIRCLE AREA = _pi * r ^ 2
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
HolmesGrown Solutions
The best solutions for the best price!
http://holmesgrown.ld.net/