[Date Prev][Date Next][Thread Prev][Thread Next][Thread Index]
Re: [XaraXtreme-dev] Re: configure.in:305: error: possibly undefined macro: AM_GNU_GETTEXT
- From: Luke Hart <lukeh@xxxxxxxx>
- Date: Mon, 05 Jun 2006 16:03:15 +0100
- Subject: Re: [XaraXtreme-dev] Re: configure.in:305: error: possibly undefined macro: AM_GNU_GETTEXT
Israel G. Lugo wrote:
Luke Hart wrote:
I was following the instructions for another package (I've forgotten
which one, thought). I suspect that using links will ensure that the
latest version is always used, rather than the files no longer
matching the version of the libraries, etc. on a users machine.
The problem with using symlinks for these files is one of portability:
systems might not have the files in the expected location, or they might
not have them at all. Personally, I would not use the -s flag, but
include the files in the package instead. If we think that part of the
whole purpose of a configure system is to have maximum portability, then
it logically follows that we should include the necessary tools for the
package to configure itself.
The files generated by autoreconf are all machine-independent anyway
(they're mostly shell scripts and their purpose is precisely to be
portable). The maintainer just needs to keep the files reasonably up to
date, which is easy enough, and that way the package is much more
self-sufficient.
Israel
I was answering a different question to the one you think I was
answering 8-). The question was why do we recommend that users who have
checked the source out of SVN, use the 'autoreconf -f -i -s'. I agree
with you entirely about not using that flag to create the release
tar-ball, but in the case of a user using it on his/her own system I can
can see advantages.
Luke