[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#21215: Bad load-path in 50psgml-init.el?



Hi,

	[Closed bug, moved to debian-policy. Please follow up to
	thepolicy list only]

>>"Davide" == Davide G M Salvetti <salve@debian.org> writes:

Davide> I think there's a mistake in the load-path set by both
Davide> emacs19|20 versions of 50psgml-init.el.

	This has already been fixed by the next upload ;-). Also, vm
 has been fixed as well.

Davide> Also, psgml currently ships two 50psgml-init.el versions, only
Davide> differing in the emacsen name used in the load-path setting.

Davide> It could ship just one, to be installed in
Davide> /etc/emacs/site-start.d/ by making use of the variable
Davide> `debian-emacs-flavor', whose value is a symbol representing
Davide> the emacsen version actually running.

	That would be a bug. You see, psgml only installs for two
 flavours of emacsen, emacs{19,20}; and it sets variables based on the
 presumption that psgml is indeed available. Putting it in
 etc/emacs/site-start.d/ is bad, since neither of the directories
 /usr/share/emacs/site-lisp/psgml and /usr/share/xemacs19/site-lisp/psgml
 should be in the load path, and there fore psgml is not available for
 xemacs, though the start file shall be run.

	Oh, though at the moment psgml does exist in xemacsen, and
 happens to be at the same version, this is not guaranteed to be so;
 as a stand alone psgml package is far more nimble. Even when XEmacs
 unbundles the software, the unbundled and free standing versions may
 have a mismatch.

	Also take vm, which is only supported on emacs19 in this
 incarnation (it does come bundled in with XEmacs). 

	I think it would be presumtuous (and quite likely erroneous)
 of me to set variables for the bundled versions, especially
 since I have no idea what the XEmacs maintainers have done
 about variable setting.

	I move for a clarification of the emacs policy to ensure that
 I do not have start files from packages I do not have access
 to. psgml and vm stand alone packages are not commonly available for
 all emacsen flavours, and hence do not insinuate themselves
 everywhere, and this should be the recommended behaviour.

Davide> For example:
Davide> (setq load-path (cons (concat "/usr/share/" (symbol-name
Davide> debian-emacs-flavor) "/site-lisp/psgml") load-path))

	emacs19 does not seem to define debian-emacs-flavor. I haveg
 to do it manually in my .emacs.

	manoj
;;
;; This is the first few line from my .emacs 
;; email me if you want emacs-vers.el
;;
(load-file "~/lib/emacs/emacs-vers.el")
(if (emacs-type-eq 'fsf)
    (if (emacs-version=  19   )
        (progn
          (setq debian-emacs-flavor 'emacs19)
          (load "debian-startup")
          (debian-startup 'emacs19))))

-- 
 "Of all the tyrannies that affect mankind, tyranny in religion is the
 worst." Thomas Paine
Manoj Srivastava  <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E


--
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: