From:	"Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To:	"DJGPP Workers Mailing List" <djgpp-workers AT delorie DOT com>
Subject:	Minor bug (feature?) in /dev/env support
Date:	Wed, 3 Jan 2001 22:35:42 +0100
Message-ID:	<NEBBIOJNGMKPNOBKHCGHGEEOCAAA.tim.van.holder@pandora.be>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id QAA17897
Reply-To:	djgpp-workers AT delorie DOT com

Hi,

I noticed an annoying thing when running the mkinstalldirs script
that comes with automake. Besides the fact that it will try to
create /dev and /dev/env (because they don't exist), this does
not result in the creation of /dev and /dev/env directories.
Instead, a /dev dir is created, and an env subdir is created in
the current directory.
The problem seems to be /dev. In bash, using completion on
/dev/env/ yields no result (even when there is an actual /dev/env
directory on the current drive), but /dev seems to resolve to the
current directory (yet a test -d on it fails).
Would it be possible to adjust this so a /dev path is first
treated as a regular path, with the magic only kicking in if
there is no corresponding real dir (as seems to happen for the
contents of /dev/env/? If not, I believe /dev and /dev/env
should be presented to apps as real, existing directories (so
mkinstalldirs will not try to create them).

- Raw text -