From:	pjfarley AT dorsai DOT org (Peter J. Farley III)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Suggestion for future DJGPP development -- depend on bash
Date:	Wed, 17 Sep 1997 00:39:08 GMT
Organization:	None
Lines:	55
Message-ID:	<341f246b.3479011@snews.zippo.com>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 970916154550 DOT 25597K-100000 AT is>
NNTP-Posting-Host:	news.newsdawg.com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
<Snipped>
>On Tue, 16 Sep 1997, Peter J. Farley III wrote:
>
>> Obviously, that is a good solution.  Until then, however, I just thought
>> there ought to be a way (and no, I don't know what it is yet) to automate
>> such a process
>
>The only way I know of is to submit a list of filename changes to
>DJTAR when you unzip the source distribution (if it is in the .tar.gz
>format).  But this requires to extract the file with the list of
>changes first.

Thanks, Eli.  Maybe that is a start in the right direction.  Might be
something the package originator/builder could do, with the right
tools.

>> One small incompatibility between DJGPP and unix systems that could,
>> perhaps, be addressed in a future release is to use more unix-standard
>> directory structures (like /usr/bin, /usr/lib, /usr/include, etc.) for a
>> higher degree of compatibility with the assumptions made for the unix
>> environment.  Just another suggestion.  DJGPP currently allows, but does not
>> require it.  Maybe that should be strengthened to at least a *suggested*
>> structure, with the option to do something different still allowed, though
>> discouraged.
>
>I don't think DOS users will like such a suggestion.  But even if they
>did, this won't work, because of the multiple drives issue.  You will
>need to have /usr/bin etc. on *every* disk you have installed on your
>system, for the Unix assumptions to hold at all times.  (Even the RAM
>drive where the temporary directory resides should have these, because
>some programs actually chdir to the temp directory to do something.)
>
>The only viable solution is what the DJGPP port of Bash does: it
>allows you to map one drive to the root, and reference others with the
>//d/dir trick.  But I have seen cases where even this isn't good
>enough.

Understood.  I myself would probably object if I didn't have a JAZ
drive to isolate my DJGPP work on.

OTOH, if one is setting up this directory structure *only* when doing
a re-build, perhaps it is not such a burden.  Only some DJGPP users,
after all, are going to want to do a re-build in the first place.

However, I will bow to this objection for ordinary, "all the time"
tool usage and availability.  I withdraw it, though obviously
reserving the right to use such a setup myself (as we all can do, if
we wish).

I'm curious, though -- in what cases did bash's sysroot and //d/dir
trick *not* work?

----------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org)

- Raw text -