On Fri, Nov 08, 2013 at 09:37:06AM -0500, Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11/8/2013 4:09 AM, Karel Zak wrote:
> > On Thu, Nov 07, 2013 at 07:32:18PM -0500, Phillip Susi wrote:
> >> -----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).
> > 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.).
> So if you don't want to do the tests and just
> generate the original tarball, make dist would do the trick right?
yes
> Yet it seems to leave files in the tarball that are NOT in the
> official release.
Yes, for example .gitignore files etc.
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
