[ESS] Emacs 23.1 is out

Marc Schwartz marc_schwartz at me.com
Tue Aug 4 22:24:23 CEST 2009

On Aug 4, 2009, at 2:00 PM, Rodney Sparapani wrote:

> Marc Schwartz wrote:
>> FWIW, here is my shell script to build Emacs 23 from their CVS on  
>> OSX. This is a modification of the script that I had been using on  
>> Fedora Linux with 23 for quite some time. The anti-aliased fonts  
>> for Linux, as compared to the prior versions of Emacs, is a  
>> blessing to readability on LCD/LED panels.
>> cvs -z3 -d:pserver:anonymous at cvs.sv.gnu.org:/sources/emacs co emacs
>> cd emacs
>> ./configure --with-ns
>> make bootstrap
>> make
>> make install
>> sudo cp -r nextstep/Emacs.app /Applications/Emacs.app
>> I don't have any MacPorts stuff on my system any longer, as I found  
>> their version dependencies on several packages to be overly  
>> problematic. It is easier just to get the individual packages from  
>> upstream.
>> HTH,
>> Marc Schwartz
> Hi Marc:
> I'll have to give it another try.  Although, I have been generally  
> hostile to packaging systems like Debian and MacPorts, I can't agree.
> I suppose Emacs is a special case since OS X ships with terminal  
> Emacs and therefore many of the prereqs are already there  
> (similarly, ESS is
> a special case since it only depends on emacs).  However, have you
> ever tried to compile subversion package by package?  I have and I
> can tell you that there are so many prereqs that it can NOT be easily
> done.  In fact, each prereq is another point of potential failure to
> such an extent that I was without subversion for more than a year
> until we moved to a new system on which I installed Blastwave.
> Rodney

Hi Rodney,

I guess we are drifting further OT here, but with specific reference  
to SVN, why compile from source when current universal binaries are  


and it has all of the required modules, etc. that I have found to be  
needed. Perhaps your local requirements are more complicated than  
mine, which is a pretty simple single user configuration with a local  
repo. In fact, I stopped using Apache recently, which I had been using  
all along on Fedora, and am now just using SVNServe. It just  
simplifies my installation and management and I don't really need all  
of the additional Apache functionality on my system.

I am not biased against packaging systems generally. When I was on  
Fedora, I did not mind using 'yum' at all, since it was Fedora release  
specific relative to versioning issues and was typically up to date  
with upstream releases.

With MacPorts, I had found several situations where they were behind  
on versions and/or their packaging dependencies resulted in conflicts/ 
duplication with either the existing OSX installation or with non- 
MacPort installed applications. It got to be a headache keeping track  
of differing versions of the apps and so I just removed all MacPorts  
stuff and get binaries (where available) from upstream. There have  
only been a few things that I needed to compile from source (eg. Emacs  
and pkg-config) and they have been no-brainers.



More information about the ESS-help mailing list