Re: MELPA BBDB - bbdb-version
On Sat Nov 21 2015 George McNinch wrote: > This behavior of a MELPA install is what I was trying to report. > Surely there is *some* way to have the MELPA install process > "properly make" BBDB? I do not know many details about MELPA. Yet it uses an automated scheme where I was told it was not really compatible with the automake rules used by BBDB. Roland -- ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: MELPA BBDB - bbdb-version
Hi-- RW> On Sat Nov 21 2015 George McNinch wrote: >> That was actually inaccurate - I had failed to snip a setting of >> load-path pointing to a directory for bbdb that I had populated >> via git (and that seemed to be the version of bbdb being used). RW> Which git repository did you use? The "official" repository is RW> git.savannah.nongnu.org/bbdb.git >> , | bbdb-version is a variable defined in ‘bbdb-site.el’. | >> Its value is "@PACKAGE_VERSION@" ` RW> You need to properly `make' BBDB (see the README file in the RW> repository) in order to get a meaningful value assigned to RW> bbdb-version. The version I have via *git* works fine for me. RW> If you just compile the elisp files from the git repository and RW> also when you get BBDB from Melpa the variable bbdb-version has RW> the meaningless value "@PACKAGE_VERSION@". This behavior of a MELPA install is what I was trying to report. Surely there is *some* way to have the MELPA install process "properly make" BBDB? Well, perhaps this is not such a huge issue. -gm -- ++ George McNinch ++ http://gmcninch.math.tufts.edu -- ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: MELPA BBDB - bbdb-version
On Sat Nov 21 2015 George McNinch wrote: > That was actually inaccurate - I had failed to snip a setting of > load-path pointing to a directory for bbdb that I had populated via git > (and that seemed to be the version of bbdb being used). Which git repository did you use? The "official" repository is git.savannah.nongnu.org/bbdb.git > , > | bbdb-version is a variable defined in ‘bbdb-site.el’. > | Its value is "@PACKAGE_VERSION@" > ` You need to properly `make' BBDB (see the README file in the repository) in order to get a meaningful value assigned to bbdb-version. If you just compile the elisp files from the git repository and also when you get BBDB from Melpa the variable bbdb-version has the meaningless value "@PACKAGE_VERSION@". Roland -- ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
MELPA BBDB - bbdb-version
In my report last week with subject header "eudc conversion to bbdb (in bbdb3.1.2?)" I noted bbdd-version => 3.1.2 and I claimed I was using the MELPA bbdb. That was actually inaccurate - I had failed to snip a setting of load-path pointing to a directory for bbdb that I had populated via git (and that seemed to be the version of bbdb being used). The gist of that earlier report is unchanged (and I have now filed a bug-report against EUDC about that matter), but: when I *don't* use my "local" version of bbdb obtained from git, but instead use the MELPA version of bbdb, bbdb-version has a strange value: In fact, describe-variable reports: , | bbdb-version is a variable defined in ‘bbdb-site.el’. | Its value is "@PACKAGE_VERSION@" ` Presumably this is related to some ELPA-packaging issue? (Or have I don't something wrong on this end?) -george -- + + + George McNinch + + + http://gmcninch.math.tufts.edu -- ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
