On 04/07/2012 05:48 AM, Akim Demaille wrote: > Hi! > > I would like bison to used gnulib's build-aux/po/Makefile.in.in, > but I don't understand how I am supposed to do that. bison's > bootstrap is sync'ed with that of gnulib (the current master).
Revisiting this topic, WHY are we trying to use gnulib's build-aux/po/Makefile.in.in? Either it matches the version of Makefile.in.in that gettextize would have installed for you in the first place, or it doesn't match and you face the problems that hit libvirt this week. Can I get some more justification for why this change was made in the first place, in case we decide that it is better to revert Jim's patches to bootstrap that force the latest Makefile.in.in into a project? > > We do have "gettext" listed in our gnulib_modules (not > "gettext-h"), and autopoint is fired, as expected, but > gnulib-tool does not override these files. The corresponding > node of the documentation is not clear about this. Ah, maybe this explains it. If you use the 'gettext-h' module, like libvirt does, you want to support arbitrary gettext versions (including 0.17); if you use the 'gettext' module, then you are stating that you want to use the latest and greatest gettext, even if that means it is newer than the current stable gettext release. That is, maybe it sounds like we should _only_ be copying the Makefile.in.in into the project if the 'gettext' module is in use, which means the copy should not be done as part of 'bootstrap', but as part of 'gnulib-tool' installing the 'gettext' module. -- Eric Blake ebl...@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
