Hi,
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.
So far, I undestood rationales behind this.
But why in clean target? This makes large
also sprach Osamu Aoki [EMAIL PROTECTED] [2004.10.25.2114 +0200]:
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.)?
It's in the clean target precisely so that it becomes part of the
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
Hi,
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.
So far, I undestood rationales behind this.
But why in clean target? This makes large
also sprach Osamu Aoki [EMAIL PROTECTED] [2004.10.25.2114 +0200]:
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.)?
It's in the clean target precisely so that it becomes part of the
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
6 matches
Mail list logo