[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Search]
Unidentified subject!
- To: "T. V. Raman" <raman@xxxxxxxxxxx>
- Subject: Unidentified subject!
- From: "James R. Van Zandt" <jrv@xxxxxxxxxxx>
- Date: Sun, 10 Mar 2002 09:51:02 -0500 (EST)
- Resent-Date: Sun, 10 Mar 2002 13:49:49 -0500 (EST)
- Resent-From: emacspeak@xxxxxxxxxxx
- Resent-Message-ID: <"krEugB.A.z8E.dm6i8"@hub>
- Resent-Sender: emacspeak-request@xxxxxxxxxxx
Raman -
I agree that Debian has its own ways of doing things. Usually, the
object is to "do the right thing", maintain maximum flexibility for
the local sysadmin, and minimize his workload. In that order.
In this case, the Debian policy allows a sysadmin to install and even
run several flavors of emacs (e.g. emacs20, emacs21, and xemacs21) at
the same time, while ensuring that when any emacs loads compiled lisp
files for an add-on package like emacspeak, it gets files compiled by
that version and flavor. (I believe that other Linux distributions,
and other Unixes for that matter, depend on compiled lisp files being
compatible across flavors and versions.) One implication is that when
an add-on package is installed or upgraded, it must be compiled by
each installed flavor of emacs. Of course, the files compiled by each
flavor have to be put in separate directories. (I suppose one could
leave a copy of the source files in each of those directories, but I
don't see the point of that.)
I admit that implementing this policy requires a lot of machinery
that is hard to keep in working order.
- Jim Van Zandt
Date: Sat, 9 Mar 2002 14:36:33 -0800
To: "James R. Van Zandt" <jrv@xxxxxxxxxxx>
Cc: Hans Zoebelein <hzo@xxxxxxxxxxx>, blinux-announce@xxxxxxxxxxx,
emacspeak@xxxxxxxxxxx, Gregory Rosmaita <oedipus@xxxxxxxxxxx>,
oedipus@xxxxxxxxxxx, "Dm. Paduchih" <paduch@xxxxxxxxxxx>
Subject: Debian package emacspeak_15-3.deb
In-Reply-To: <m16jo30-00017oC@xxxxxxxxxxx>
References: <m16jo30-00017oC@xxxxxxxxxxx>
X-Mailer: VM 6.84 under Emacs 20.6.1
From: "T. V. Raman" <raman@xxxxxxxxxxx>
Reply-to: raman@xxxxxxxxxxx
Is there a good reason why you're moving the compiled .elc
files out of the install directory?
This is why your previous package broke--
it's also different than how other Linuxuns install emacs.
If there is something more here than Debian wanting to be
different one would like to know:-)>>>>> "James" == James R Van Zandt <jrv@xxxxxxxxxxx> writes:
James> I am uploading a new Debian package for emacspeak
James> 15. I have changed the load-path settings, so
James> the compiled version appears before the source.
James> This should speed both startup and operation.
...
-----------------------------------------------------------------------------
To unsubscribe from the emacspeak list or change your address on the
emacspeak list send mail to "emacspeak-request@xxxxxxxxxxx" with a
subject of "unsubscribe" or "help"