[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Appropriately Expanding a .tar.gz File
- From: "Aaron D. Turner" <aturner best com>
- To: redhat-list redhat com
- Subject: Re: Appropriately Expanding a .tar.gz File
- Date: Sat, 2 Jan 1999 12:23:18 -0800 (PST)
-----BEGIN PGP SIGNED MESSAGE-----
Kurt,
You realize you have to *compile* mutt before it will work? :-)
There's probably a 'configure' script, which you run. Run:
./configure --help
for help. Then run 'make' and if it compiles correctly 'make install'.
Generally, things like this get installed in /usr/local/bin
- --
Aaron Turner | Either which way, one half dozen or another.
aturner pobox com | Check out the Red Hat Linux User's FAQ Online!
www.pobox.com/~aturner | http://www.pobox.com/~aturner/RedHat-FAQ/
All emails from this account are PGP signed. Lack of a signature is "bad".
PGP Key fingerprint = FB E1 CE ED 57 E4 AB 80 59 6E 60 BF 45 1B 20 E8
On Sat, 2 Jan 1999, Kurt Harper wrote:
> There is a slough of files that come out of that tar.gz
> file. My first thought is to make a subdirectory of /usr/bin/
> --where the present mutt executable resides-- and expand
> the files into it, then to put a symbolic link to the mutt
> executable in the mutt subdirectory into /usr/bin/. Is that the
> proper way to do it?
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNo6ASTM3jpXy1kJtAQFR5QP+La4A4iO9txcPmA0+6LcMME08JrND155n
PXoA1luzCfLqvWWbztbCMNg7qdYtct/rtktprD0nwwgO0yDohs1Nf5N8r3TYJLUk
fXSQau+v215woWQlC0dlPo40jATQkZpDnss1anpcDOXj6v0w1xb0QSHRBwMN0u/J
UPzXEDUUatk=
=fnlF
-----END PGP SIGNATURE-----
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]