From: "Tim Van Holder" To: "Eli Zaretskii" Cc: Subject: Re: gettext pretest available Date: Sun, 4 Mar 2001 10:00:55 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <7263-Sun04Mar2001002538+0200-eliz@is.elta.co.il> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Also, I don't understand the ``outdated'' part. The binary on SimTel > is based on the latest official release of Emacs. My mistake - I should have checked. I thought there had been no release of 20.7 > I don't plan to change the Emacs installation tree. The DJGPP port is > set up to build and install in-place. If you move it, you will have > to set all kinds of environment variables to let Emacs find its files, > or hack the epaths.h header to have the relevant directories > hard-wired there, in which case they will not work on someone else's > machine. Odd - I built emacs 20.7 from the regular configure, with prefix=/dev/env/DJDIR. This worked fine; and I've now moved my DJGPP tree to a different drive and emacs still works fine. One thing I have yet to fix is that emacs tends to turn /dev/* into :/dev/*; but that is pretty harmless. I did some other tweaking here and there (too long ago to remember), but IIRC there was no major work involved. Given that emacs can find its files just fine if put in $DJDIR/bin and $DJDIR/share/emacs, I didn't see a real reason to banish it to $DJDIR/gnu/emacs, except perhaps that building in-place does not require having enough space for two lisp trees; then again, there is no reason why you should keep the source tree around after a 'make install'. > What's wrong with %DJDIR%/gnu/emacs/, anyway? Are there any real > reasons for changing the current defaults? There's nothing _wrong_ with it, except that it adds yet another directory to the path. Plus, every other DJGPP package puts its binaries in $DJDIR/bin (I think - didn't check all packages to see if that's true). But since that is the current default, I guess we're stuck with it.