> Please correct me if I am wrong: doesn't your approach require that
> $pkgdatadir is properly defined at compile time, though it is
> normally required by make only at install time?
The standard autotools way of "baking in" directories and such into
installed files is to do so at build time, using in the case of C/C++
things like
... -DDATADIR=\"$(datadir)\" ...
The analogous mechanism here is to rewrite the string, since the
bbdb-site.el file is not compiled so we cann't bake the directory into
bbdb-site.elc. This is what I've done in the latest patch.
I suppose one could hotwire "make install" to rewrite the string, but
the usual convention is that what gets installed is exactly what was
built, just copied into the right places, and *maybe* at most debugging
info stripped.
One argument is: it's got to go *somewhere*, so why not in bbdb-site.el
where people would expect it? Principle of least surprise.
--Barak.
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
