On Thu Feb 6 2014 Steve Purcell wrote: > Yup, it would be broadly reasonable for us to replace > @PACKAGE_VERSION@ with our version in .in files, but we're not > keen to provide a general substitution mechanism. > > In this particular case, the author could include a ;; Version: > @PACKAGE_VERSION@ header in the main elisp file, then bbdb-version > could extract that string. The code would then work in MELPA too, > because we update the Version: header.
The whole point of using @PACKAGE_VERSION@ is certainly that the package version is defined exactly once in the file configure.ac of a package. Then autoconf substitutes everywhere @PACKAGE_VERSION@ by the package version defined in that file. ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
