From alsa-user-owner@alsa.jcu.cz  Sat Mar 13 07:00:10 1999
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id GAA16402
	for <alsa-user@alsa.jcu.cz>; Sat, 13 Mar 1999 06:58:26 +0100
Received: from TUX.MIT.EDU by MIT.EDU with SMTP
	id AA26219; Sat, 13 Mar 99 00:57:54 EST
Received: by tux.mit.edu (8.8.7/4.7) id AAA21257; Sat, 13 Mar 1999 00:58:16 -0500
To: alsa-user@alsa.jcu.cz
Subject: Re: apropos build [ prep | config | all | clean | rpms ]
References: <004301be6d0f$e220f3e0$0100007f@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
From: amu@MIT.EDU (Aaron M. Ucko)
Date: 13 Mar 1999 00:58:16 -0500
In-Reply-To: "Bill Hogan"'s message of "Fri, 12 Mar 1999 21:10:57 -0800"
Message-Id: <udlu2vq0w3r.fsf@tux.mit.edu>
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

"Bill Hogan" <not_quite@email.msn.com> writes:

> `config', `all', and `rpms' look reasonably familiar but I am not sure about
> `prep'.

"prep" runs autoconf and similar programs to produce configure scripts
and other automatically generated system-independent files.

If your tree is owned by an ordinary user, only "rpms" requires root
privileges.

It is worth noting that the only step "rpms" really depends on is
"prep", though it's a good idea to make sure "config" and "all" work
first.

-- 
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)

