Re: pkg/46804: Emacs Load Path issues when using emacs-nox11 w/ other packages such as flim, semi, and skk

[David Holland <dholland-pbugs%netbsd.org@localhost>]

The following reply was made to PR pkg/46804; it has been noted by GNATS.

From: David Holland <dholland-pbugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/46804: Emacs Load Path issues when using emacs-nox11 w/
 other packages such as flim, semi, and skk
Date: Wed, 22 Aug 2012 19:18:00 +0000

 On Wed, Aug 22, 2012 at 09:40:03AM +0000, OBATA Akio wrote:
  >  >  I don't understand the objection. Isn't it easier to define
  >  >  EMACSLOADPATH correctly in each of the emacs packages (which can be
  >  >  version-specific) than to try to extract it afterwards?
  >  
  > Origin of this PR is "hand-made maintenance of variables is
  > sometimes not correct".
 
 true.
 
 ah, I see the problem: I misunderstood what the issue was, because I'd
 confused it with the problem I created by sticking "nox11" in the wrong
 place when importing emacs24. So maybe I should just be quiet :-)
 
 However, if the load path we want is always based on
 ${PREFIX}/share/emacs/${VERSION}/lisp, wouldn't it be better to get
 the version with emacs -q -batch -eval '(print emacs-version)' than to
 grind the load path? (And if you use princ instead of print, it
 doesn't emit quotes and they don't need to be stripped off.)
 
 One other thing: as per earlier discussion on tech-pkg I'm still
 intending at some point to fix the emacs packages to include the major
 version in the package name (emacs20-20.7.1, emacs23-23.4.1, etc.) so
 if possible try to avoid doing anything that'll break on that...
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost