Message-ID: <001101be7f64$5d4f7c60$b4033bd4@default>
From: "Laurynas Biveinis" <lauras AT softhome DOT net>
To: <djgpp-workers AT delorie DOT com>
Subject: Re: Fw: LBInstDJ - second, improved version
Date: Mon, 5 Apr 1999 14:58:21 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-4"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
Reply-To: djgpp-workers AT delorie DOT com

-----Original Message-----
From: DJ Delorie <dj AT delorie DOT com>
To: eliz AT is DOT elta DOT co DOT il <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp-workers AT delorie DOT com <djgpp-workers AT delorie DOT com>
Date: 1999 m. Balandis 5 d. 14:45
Subject: Re: Fw: LBInstDJ - second, improved version


>
>> I agree that for everybody's safety a non-LFN directory is better, but
>> having an installer insist on that is IMHO a Bad Thing, 'cause
>> somebody might know what they are doing.  It might be a better idea to
>> check whether DJGPP.ENV is accessible via the DJGPP variable setting.

How can I do it in the installer? When DJGPP is not set and DJGPP.ENV does
not
exist?

>
>Perhaps it should warn if it detects a LFN install directory, and
>require the user confirm their choice, after warning that it may not
>work unless the user really knows what they're doing?


LBInstDJ will do so in next version. Before 0.2 release I was planning to
completely forbid
installing in LFN dir, but commented it out in last minute before uploading
so now user can install in LFN dir
without any warning. IMHO, going from one extreme to another wasn't good
thing.

Laurynas Biveinis