vm team mailing list archive

[Tim Cross <theophilusx@xxxxxxxxx>]

Blueprint changed by Tim Cross:

Whiteboard changed:
  A number of changes may be necessary to VM source files to allow
  inclusion in ELPA. The code must be released under an open source
  license. Is this an issue? Need to verify status of the add-ons.
  
  Code needs to comply with emacs standards on header/footer sections. We
  are probably pretty close. Most changes would be fairly trivial i.e.
  ensuring right number of ; in comments etc.
  
  Need to verify autoload comments are all OK
  
  Need to contact the ELPA maintainers *before* starting any work to check
  on any requirements/restrictions. Have not done this as first needed to
  get feedback from dev team.
  
  Uday: Seems like a good idea.  If there will be an easy way for Emacs-
  users to download and install packages, we should use it.  License is a
  non-issue, we are under GPL.  Coding style will require some work, but
  not a big issue.  My main concern is whether ELPA's installation
  mechanism will be able to accommodate our "build".  There might be
  changes needed.
+ 
+ Email sent   2010/08/15 to the ELPA maintainers asking for some
+ information on what would be required in order to create a VM ELPA
+ package. In particular, asked for information on using autoconf
+ configure script, handling of non-elisp code., handling of documentation
+ files etc.

-- 
Add VM to the Emacs Lisp Package Archive
https://blueprints.launchpad.net/vm/+spec/vm-elpa