From: Sven Joachim <svenjoac@gmx.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Load path and custom compiling cvs on Debian
Date: Mon, 17 Dec 2007 15:47:57 +0100 [thread overview]
Message-ID: <874peh74yq.fsf@gmx.de> (raw)
In-Reply-To: 8763yx668f.fsf@lion.rapttech.com.au
On 2007-12-17 10:05 +0100, Tim X wrote:
> There are a number of things you need to do to get a CVS build of emacs
> work with debian managed elisp packages. The debian version of emacs 22 is
> modified to handle this and you will need to do the same sort of
> modifications to make this work with your CVS version.
>
> The best way to do this is grep the files in the lisp directory of the
> debian version of emacs 22 for the string 'debian' (make it case
> insensitive).
Not really. The best way to do this is to download and unpack the
Debian emacs22 source package, e.g. with "apt-get source emacs22".
There you can find all the patches in the debian/patches subdirectory.
> I can't remember all the files that are modified, but it does include
> startup.el and I think paths.el and possibly some others.
>
> You will also need to make the site-lisp of the installed CVS version
> (i.e. probably /usr/local/share/emacs/23.x/site-lisp a symbolic link to
> /usr/share/emacs22/site-lisp.
Could you elaborate on that? The Debian packaged Emacsen look for site-lisp
directories both under /usr/share and under /usr/local/share.
> Note also that when emacs is built, aI think it dumps an image of itself to
> speedup startup. This means you cannot just modify startup.el and have it
> work. You need to modify it and then build emacs.
Correct.
> At one stage there were some emacs22 snapshot packages being done - maybe
> google to see if you can find someone else who has done all the hard work
Snapshots of the Emacs trunk are still built weekly by Romain Francoise,
see http://emacs.orebokech.com/. That's probably the best starting
point for building a debianized unicode-2 Emacs.
Sven
next prev parent reply other threads:[~2007-12-17 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5036.1197654377.18990.help-gnu-emacs@gnu.org>
2007-12-15 2:43 ` Load path and custom compiling cvs on Debian 方旭亮
2007-12-17 9:05 ` Tim X
2007-12-17 10:04 ` Thierry Volpiatto
2007-12-17 14:47 ` Sven Joachim [this message]
2007-12-19 7:26 ` Tim X
2007-12-14 17:46 John Wells
2007-12-14 18:23 ` Peter Dyballa
2007-12-14 19:44 ` John Wells
2007-12-14 22:47 ` Peter Dyballa
2007-12-15 4:28 ` Kevin Rodgers
[not found] ` <mailman.5054.1197784667.18990.help-gnu-emacs@gnu.org>
2007-12-18 7:09 ` Tim X
2007-12-18 11:46 ` Richard G Riley
2007-12-19 7:31 ` Tim X
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874peh74yq.fsf@gmx.de \
--to=svenjoac@gmx.de \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).