On Mon, 25 Oct 2004, Osamu Aoki wrote:
> I have question about handling of config.guess and config.sub in source
> package. I have read autotools-dev README.Debian. So I understand these
> need to be the latest ones whenever we compile the source.
Good :-)
> But why in clean target? This makes large diff.gz with useless patch.
> Why not at the start of config.status after dh_testdir (or include it to
> dh_testdir.)?
Use the link method, it won't increase the diff. It is in the clean target
because there isn't a proper target to transform the source before packing
and after unpacking.
The link method basically rm f config.sub and config.guess on clean (which
mean they will not show up on the diff) and ALSO rm -f them and symlink them
to /usr/share/misc/config.{sub,guess} before calling configure. The price
is a build-depends on autotools-dev. Some people don't like this because
what you get when you initially dpkg-source -x is not exactly what will be
used if you try to dpkg-buildpackage.
> Can anyone point me to where to find ratinale of this practice?
Some people don't like the symlink method, and it is better to have a bigger
diff than to have a permanently static config.sub/guess that will require an
upload later.
> (At least when ever I build with dpkg-buildpackage, it runs clean first
> so this cosmetic difference has no binary impact.)
That's why the clean target was used, since there is no proper target, and
in practice the clean target works.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
