From: norseman <norseman@firstlight.net>
To: Justin Zygmont <jzygmont@solarflow.dyndns.org>,
linux-msdos@vger.kernel.org
Subject: Re: 1.2.0 binary install
Date: Fri, 23 Jan 2004 15:01:56 +0000 [thread overview]
Message-ID: <40113764.FAA01B39@firstlight.net> (raw)
In-Reply-To: Pine.LNX.4.44.0401231709390.31850-100000@solarflow.dyndns.org
Justin Zygmont wrote:
>
> > Seriously: I think the binary install should do exactly the same
> > that the (excellent) source install does; i.e. it should put
> > exactly the same files in exactly the same locations (/usr/local)
> > that are used by ./configure, make, [become root] make install. It
> > should just free the dummy user from the compilation step, for
> > which he/she most probably lacks the tools, and would be
> > confronted with (to her/him) incomprehensible error messages
> > because of that. It should (like the source install) also be
> > independent of freedos, because dosemu itself is independent of
> > it. Like the source install, it should ask which directory is the
> > 'C drive'. If user/dummy does not know, it should be pointed out
> > that some form of DOS is needed, and installation of freedos offered.
>
> well, a compresed tar file will extract itself relative to your current
> path, so you can't really have it install to /usr/local by default, it's
> not usually a problem anyways. There is the RPM that might be preferrable
> for you, dosemu is much easier than it used to be.
>
sound the gong!
tar -xzfP tarfile will install absolute if
tar -czfP tarball / was used
OK-OK simmer down class.
cd someplace with space (/tmp)
mkdir a dummy directory (/tmp/d)
cd the dummy dir (pwd -> /tmp/d )
mkdir usr
mkdir usr/local
mc /usr/local ./usr/local
arrow down to dosemu
<F5> and copy branch
<F10>
tar -czPf /anotherplace/tarfile /
get the picture?
done?
clean up your disk!
the -P retains leading "/"
Steve Turner
norseman@firstlight.net
next prev parent reply other threads:[~2004-01-23 15:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 19:27 1.2.0 binary install Jan Willem Stumpel
2004-01-23 8:59 ` Ged Haywood
2004-01-23 21:03 ` Jan Willem Stumpel
2004-01-23 14:07 ` norseman
2004-01-23 22:38 ` Bart Oldeman
2004-01-23 15:45 ` norseman
2004-01-24 0:34 ` Bart Oldeman
2004-01-24 12:24 ` norseman
2004-01-24 23:16 ` Justin Zygmont
2004-01-24 18:00 ` norseman
2004-01-25 0:05 ` Bart Oldeman
2004-01-23 21:57 ` Bart Oldeman
2004-01-23 14:40 ` norseman
2004-01-23 23:08 ` Bart Oldeman
2004-01-23 16:30 ` norseman
2004-01-24 0:48 ` Bart Oldeman
2004-01-24 13:16 ` Ged Haywood
2004-01-24 12:48 ` Appology to Bart norseman
2004-01-24 15:16 ` 1.2.0 binary install Jan Willem Stumpel
2004-01-23 22:12 ` Ged Haywood
2004-01-23 22:15 ` Justin Zygmont
2004-01-23 15:01 ` norseman [this message]
[not found] <Pine.LNX.4.44.0401231719490.31850-100000@solarflow.dyndns.org>
2004-01-23 14:50 ` norseman
[not found] <40128B80.8060503@my.home>
2004-01-24 17:38 ` Bart Oldeman
2004-01-24 18:29 ` Jan Willem Stumpel
2004-01-24 19:08 ` Bart Oldeman
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=40113764.FAA01B39@firstlight.net \
--to=norseman@firstlight.net \
--cc=jzygmont@solarflow.dyndns.org \
--cc=linux-msdos@vger.kernel.org \
/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