Date: Tue, 16 Sep 1997 15:46:32 +0300 (IDT) From: Eli Zaretskii To: djgpp AT delorie DOT com Subject: Re: Suggestion for future DJGPP development -- depend on bash In-Reply-To: <341defd7.5403236@snews.zippo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk 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. > 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.