Generating release from git
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
How do you generate the release tarball from the git repo? I thought it would be to run make dist, but it seems the real release tarball is bootstrapped with autogen.sh, but NOT configured, and make dist generates a tarball that is already configured.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCgAGBQJSfDESAAoJEJrBOlT6nu75wf4IANb9Bi8txCj1XDA10vThctmv 71+d3YRpvJIhItmgXidPGpuRRBJmQEGWhiLKeYan7WRoZBonniG3KdiEtHTGgqvS rZIOXBLcoxmisL6LQb0X10Zj3kPK7N3qQfh3rm4p51ATVBKxb82E6DhnyHgN2Kbt 3LZaMrfzGdXHzVl7tWH83gFpf6m3jMixisA87hbU48dmd4PC71e8T3fsCzE4uPkx X5P59qv84PRj7Z7Kx+au3j3cYiidVR61lJRu110MyS1HnpylSjNU2iND+JTmxw/y VxX5zaaPyEqnDu0D1TUrz5p8SNxfVKp0P0n4jB93+jkZy663yVnsjf1cCD93iZw= =bU9G
-----END PGP SIGNATURE-----
Karel Zak
maintainerQuoted 7 lines · Phillip Susi
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512How do you generate the release tarball from the git repo? I thought it would be to run make dist, but it seems the real release tarball is bootstrapped with
autogen.sh, but NOT configured, and make dist generates a tarball that is already configured.
if you have autotools based build system than
make distcheck
is only way how to generate reliable and consistent tarballs. My release sequence is usually:
git tag -s -m "release ${UL_NEXT_RELEASE}" ${UL_NEXT_RELEASE} git clean -xfd
./autogen.sh
./tools/config-gen devel # or ./configure
make -j
make distcheck
note that build system uses tools/git-version-gen to get release version so "git tag" is necessary to get proper release number.
Karel
Signature · 2 lines
Karel Zak <[email protected]> http://karelzak.blogspot.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 9 lines · Karel Zak
Quoted 7 lines · Phillip Susi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
How do you generate the release tarball from the git repo? I thought it would be to run make dist, but it seems the real release tarball is bootstrapped with
autogen.sh, but NOT configured, and make dist generates a tarball that is already configured.
Quoted 3 lines
if you have autotools based build system than
make distcheck
Doesn't this do the same thing as make dist, only with a make check and such thrown in? So if you don't want to do the tests and just generate the original tarball, make dist would do the trick right? Yet it seems to leave files in the tarball that are NOT in the official release.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSfPcSAAoJEJrBOlT6nu75nRkIAMwz+hVP4fswX4y+V3Xlu33I avv8KO54Dq7UpOz6f52/PsFAimCNrqD8kM/1Ye2sLcmoWUGZriZooc8Rj2LZJiEu XRqTf3m4tE9pFRNfgTy3ujGJILQfzOtWzCKpW8j54zK1ygfgBEu6bzFVLFQzIzH0 L3K45UTMss0x1QXWnBf9lRDtroeZk41Q5lZHmI24nRGb68Vck2EyZr2NdHukJldk v/vUDBhTNgsbYk+Ihn49Ri2Y3IgnTjh0c9WlfOF7WR4jPTSQ0kWHLTau9qB37jch XtXT8PTn8uSF4PPeQDJnR4XUekBwEZoiFoL8jDgoyM2erBYpC7iB7aAJoxfxhv8= =vp2J
-----END PGP SIGNATURE-----
Karel Zak
maintainerQuoted 12 lines · Phillip Susi
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 8 lines · Karel Zak
Quoted 7 lines · Phillip Susi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
How do you generate the release tarball from the git repo? I thought it would be to run make dist, but it seems the real release tarball is bootstrapped with
autogen.sh, but NOT configured, and make dist generates a tarball that is already configured.
I see that after "make dist" the tarball is not configured (for example there is no config.h).
Quoted 6 lines
Quoted 3 lines
if you have autotools based build system than
make distcheck
Doesn't this do the same thing as make dist, only with a make check and such thrown in?
Yes, it seems the same, but it does not call "make check" only but it also checks if the tarball is usable (it calls make, make install, etc.).
Quoted 2 lines
So if you don't want to do the tests and just
generate the original tarball, make dist would do the trick right?
yes
Quoted 2 lines
Yet it seems to leave files in the tarball that are NOT in the official release.
Yes, for example .gitignore files etc.
Karel
Signature · 2 lines
Karel Zak <[email protected]> http://karelzak.blogspot.com
Quoted 4 lines · On Thursday 07 November 2013 19:32:18 Phillip Susi wrote:
How do you generate the release tarball from the git repo? I thought it would be to run make dist, but it seems the real release tarball is bootstrapped with
autogen.sh, but NOT configured, and make dist generates a tarball that is already configured.
pretty sure that is incorrect. make dist produces a tarball that has autotools generated so people can run ./configure, but the tarball doesn't contain things produced by ./configure itself.
-mike