all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs 23 & Debian
Date: Fri, 26 Jun 2009 16:55:43 +1000	[thread overview]
Message-ID: <87fxdnscuo.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: h20aao$65j$1@news.eternal-september.org

Richard Riley <rileyrgdev@gmail.com> writes:

> Ben Badgley <mortecanine@peoplepc.com> 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. 

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. 


> 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. 

> | sudo make install
> `----
>
> The ./configure stage MIGHT give errors - goto Google or back here for
> specific help.
>
> Try it!
>
> regards
>
> Richard.
>
>
>
>
>
>

-- 
tcross (at) rapttech dot com dot au


  reply	other threads:[~2009-06-26  6:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1253.1245948264.2239.help-gnu-emacs@gnu.org>
2009-06-25 16:58 ` emacs 23 & Debian Richard Riley
2009-06-26  6:55   ` Tim X [this message]
2009-06-26 14:51     ` Richard Riley
2009-06-25 17:04 ` Thorsten Bonow
2009-06-26  2:12   ` Michael Ekstrand
2009-06-26  6:47 ` Tim X
     [not found] <mailman.1260.1245962363.2239.help-gnu-emacs@gnu.org>
2009-06-25 21:03 ` Thorsten Bonow
2009-06-25 20:38 Benjamin Badgley
  -- strict thread matches above, loose matches on Subject: below --
2009-06-25 16:44 Ben Badgley
2009-06-25 17:21 ` Nurullah Akkaya
2009-06-25 22:30   ` Peter Dyballa
     [not found] ` <mailman.1254.1245950536.2239.help-gnu-emacs@gnu.org>
2009-06-26  1:37   ` Giorgos Keramidas
2009-06-26  4:30     ` Nurullah Akkaya
2009-06-26  9:07     ` Peter Dyballa
     [not found]     ` <mailman.1280.1245990651.2239.help-gnu-emacs@gnu.org>
2009-06-26 18:25       ` Giorgos Keramidas
2009-06-27 14:31         ` rustom

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fxdnscuo.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.