public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Trying out Slackware
Date: Sun, 24 Jun 2007 22:53:30 -0500	[thread overview]
Message-ID: <009501c7b6dc$65c7ed10$ab00a8c0@tenstac> (raw)
In-Reply-To: <BAY141-DAV9430536F4DBA388C253DD8F140@phx.gbl>

Zach,

On slackware, forget packages once you have the system
installed. Grab the source for xyz software and read the 
install.txt or readme.txt. In most situations it's as simple as

./configure
make
make install

and some have
make test

That's if the source was set up to work with autoconf.
This is true of most software around these days, as for
the ones that don't use it, just read the install directions.
Usually all that is required is a few tweaks to makefules
to get it to build on your system.

I can see the convenience of apt and yum and all that,
but I can see the detriment too. Knowing how to build
everything from source is very valuable, and that's how
to get guaranteed compatibility, since you're using your
own runtime libraries.

Some things require more work to install on slackware,
but it doesn't bother me. As they say, engineers will 
generally keep engineering _forever_ unless at some 
time you tell them to stop :) Imagine if we could do 
this and that and this ...

  -- Doug


  parent reply	other threads:[~ UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Zachary Kline
 ` Littlefield, tyler
 ` Doug Sutherland [this message]
 ` Gaijin
   ` Littlefield, tyler
   ` Adam Myrow
     ` Gaijin
       ` ace
         ` Deborah Norling
 ` Ralph W. Reid
   ` Steve Holmes
     ` ace

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='009501c7b6dc$65c7ed10$ab00a8c0@tenstac' \
    --to=doug@proficio.ca \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).