Fri 19 Jul 2013 09:47:13 PM UTC, comment #4:
Hello.
(no, I am not an automated system, alas!) ;-)
Let me clarify "installing with elpa using the melpa repository".
MELPA (http://melpa.milkbox.net/) or Milkypostman’s Emacs Lisp Package Archive describes itself as follows:
- Up-to-date packages built on our servers from upstream source
- Installable in any recent Emacs using "package.el" - no need to install svn/cvs/hg/bzr/git/darcs etc.
- Curated - no obsolete, renamed, forked or randomly hacked packages
- Comprehensive - more packages than any other archive
- Automatic updates - new commits result in new packages
- Extensible - contribute recipes via github, and we'll build the packages
For all intent and purpose, melpa grabs the git (or other) repository, cooks it in a manner that the package.el is capable of understanding. On the user's end, package.el manages the nitty gritty of the installation.
Why this, and not the AC? Practicity: one interface to manage all supplementary packages, and to keep them up-to-date.
Maybe the recipe used by MELPA could be incompatible with recent changes to bbdb... However, other bbdb mirrors around are also defective due to recent modifications. See:
https://github.com/emacsmirror/bbdb/tree/master/lisp
Probably the changes in bbdb are generating downstream problems with the recipies generating the distributed packages or the mirroring. Indeed, the recipe for bbdb copies only the .el files from the git repository:
https://github.com/milkypostman/melpa/blob/master/recipes/bbdb
So the problem is definitely not with bbdb, and I apologize for the distraction. I just think you should be aware that the modifications are having consequences elsewhere.
(As of today, this broken bbdb has been downloaded 1115 times from the melpa repository).
I followed the procedure you described, and must note the following:
Using Ubuntu 13.04 i386, automake is version 1.11. Thus, the autogen.sh script failed (requirement of Automake 1.13)
I hacked the script to proceed with 1.11, and it did. (I do not know what might be broken inside, but at least the compilation went through.) Is 1.13 really needed?
I fail to understand the need for going through the autogeneration of the bbdb-version.el file through the ac script.
My suggestion is to leave a bbdb-version.el file in the git directory, that could be overwritten by ac if needed.
Thanks
|