From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Riley Newsgroups: gmane.emacs.help Subject: Re: emacs 23 & Debian Date: Fri, 26 Jun 2009 16:51:06 +0200 Organization: aich tea tea pea dicky riley dot net Message-ID: References: <87fxdnscuo.fsf@lion.rapttech.com.au> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1246034730 31839 80.91.229.12 (26 Jun 2009 16:45:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 26 Jun 2009 16:45:30 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Jun 26 18:45:23 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MKEYD-0004z8-NZ for geh-help-gnu-emacs@m.gmane.org; Fri, 26 Jun 2009 18:45:22 +0200 Original-Received: from localhost ([127.0.0.1]:35682 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MKEYD-0005f6-5Q for geh-help-gnu-emacs@m.gmane.org; Fri, 26 Jun 2009 12:45:21 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!news2.euro.net!feeder.news-service.com!eternal-september.org!news.motzarella.org!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 126 Original-X-Trace: news.eternal-september.org U2FsdGVkX1/+RpxVm3BVb7o9KyBL1tzGIT2F+DUWiuI8eAfpZj5oAt2TuPf96E0DUE0X6WKvAqY6dMdoZ7p9qEFYJ71rfICLxRMD2WpM5DPUDsF/8ZBkqpT6a8k9yG7Z3d3uRIuL4AU= Original-X-Complaints-To: abuse@motzarella.org Original-NNTP-Posting-Date: Fri, 26 Jun 2009 14:51:04 +0000 (UTC) X-Auth-Sender: U2FsdGVkX1+uXFhU6oksvDm2v0elN/41WlYby62vSfcyq/T2VQjEJA== Cancel-Lock: sha1:VcKFuwUuJ+5i1kunBQK2k0We8RE= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Original-Xref: news.stanford.edu gnu.emacs.help:170337 X-Mailman-Approved-At: Fri, 26 Jun 2009 12:44:25 -0400 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:65559 Archived-At: Tim X writes: > Richard Riley writes: > >> Ben Badgley writes: >> >>> 1. Where and how may a person upgrade to version 23 for Debian? >>> >>> I'm a simple 'go grab a .deb and install it' sort at this point, >>> although am getting better with using the console. So, please avoid >>> saying cvs or git, subversion. Have a friend coming over for the weekend >>> who may better explain that voodoo to me >>> >>> 2. Why did the Debian Emacs release come over as a bit hindered? >>> >>> Noticed this on the Emacs Wiki threads about Emacs on Debian. It >>> couldn't sort out what was where, or its version. There was some code to >>> attempt correcting it posted as well. >>> >>> 3. And will future Debian releases of Emacs be so? >>> >>> Hope not on this end. >>> >>> >>> >> >> I have been through this. >> >> The bottom line for me was to dump debian emacs and follow the simple >> enough instructions available from Google to get from cvs and >> compile. It really is not that difficult. I know you said you didn't >> want to hear but thats what i said at first. and the build has become a >> LOT easier than a while ago. >> >> Why did I dump debian emacs? Because they do all sorts of smart stuff >> with system files that simply confused me and anyone I asked for help >> from. The general consensus was "you're on your own" when I mentioned >> debian in #emacs irc channel! >> >> The only issue then is getting your "generally used" files from the >> emacs wiki or elsewhere that does not ship with emacs. It doesn't take >> long. I store it all in a ~/.emacs.d/lisp directory and add that to my >> loadpath as is well documented elsewhere. >> > > This is the disadvantage of that approach - you lose all that handy > pre-packaged debian emacs elisp stuff. Its one of the main reasons I use > Debian. Well, yes, but it comes with disadvantages as I outlined. And also this handy prepackaged stuff can be notoriously out of date and then you get into testing packages and extra source lines. The other main reason which I neglected to mention is that by having ALL the elisp utilties I use in my elisp directory it makes it very easy for me to Unison my emacs config between my multiple machines - my emacs is identical on all machines. > > Go to http://emacs.orebokech.com and you can get verson 23 of emacs that > is built as a deb and works with the debian emacs infastructure. Updates > happen regularly, so you stay pretty close to the head of the CVS > tree. Even better, Romain ensures the packages are pretty stable before > he releases them, so you don't get bitten by transient problems with > CVS. Actually I got bitten with this package! Plus I like to use CVS. > > >> So, uninstall all emacs stuff! >> >> Then: >> >> we go to the command line and install the stuff we need to build emacs: >> >> ,---- >> | sudo apt-get install build-essentials >> `---- >> >> then go here and read : >> >> http://savannah.gnu.org/cvs/?group=emacs >> >> Knowing what we want to do, we go to the command line change to a >> directory where you want to build emacs and do: >> >> ,---- >> | cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/emacs co emacs >> `---- >> >> Then cd into out new emacs directory and: >> >> ,---- >> | ./configure >> | make > > Actually, if your building from CVS sources, you should be doing make > bootstrap rather than just make - at least for the first time. this will > ensure all the .el files are re-built. This is documented in the > INSTALL.CVS file in the root of the source tree. Thanks for pointing that out. I had thought it was built into the makefile and dont think I have ever manually ran it! I'll check up. > >> | sudo make install >> `---- >> >> The ./configure stage MIGHT give errors - goto Google or back here for >> specific help. >> >> Try it! >> >> regards >> >> Richard. >> >> >> >> >> >> --