vm team mailing list archive

["Tim Cross" <theophilusx@xxxxxxxxx>]

Ulrich Mueller writes:
 > >>>>> On Wed, 18 Aug 2010, Tim Cross wrote:
 > 
 > > + More analysi is required, but the initial impression is thaqt
 > > ELPA + packages need to support build and installation processes
 > > that are all + elisp driven. Would likely need elisp code that
 > > would search for add-on + features, such as bbdb or w3m. Still
 > > worth further investigation, but it + looks like it may be
 > > necessary to add an all elsip based build process.
 > 
 > Moving from autoconf to some hand-made elisp build process looks
 > like a step in the wrong direction to me. VM contains also some
 > binaries (like qp-decode) that must be compiled and installed. How
 > would one handle this without autoconf?
 > 

I'm thinking more along the lines of adding a 'make elpa-package target for the
Makefile, which could possibly create an ELPA specific 'package' build and not
getting rid of autoconf et. al. I've used this technique for other package
systems. Support for ELPA is not a replacement for our existing build system,
but rather an extension to support providing ELPA packages. ELPA is more a
package installation/maintenance system, not a build system per se. 

I'm not sure how or even if it will be possible to include the qp-decode et.
al. C packages. More analysis is required. Maybe the ELPA pakage doesn't
include them or they become a separate download or ... These programs are not
essential for VM. In fact, I've not used them for a long time, preferring other
alternatives which I've found more reliable. 

Tim

-- 
Tim Cross
tcross@xxxxxxxxxxxxxxx

There are two types of people in IT - those who do not manage what
they understand and those who do not understand what they manage.
-- 
Tim Cross
tcross@xxxxxxxxxxxxxxx

There are two types of people in IT - those who do not manage what they 
understand and those who do not understand what they manage.