public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Generating release from git
Date: Fri, 08 Nov 2013 09:37:06 -0500	[thread overview]
Message-ID: <527CF712.90809@ubuntu.com> (raw)
In-Reply-To: <20131108090906.GB10401@x2.net.home>

-----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.
> 
> 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-----

  reply	other threads:[~2013-11-08 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08  0:32 Generating release from git Phillip Susi
2013-11-08  9:09 ` Karel Zak
2013-11-08 14:37   ` Phillip Susi [this message]
2013-11-08 14:56     ` Karel Zak
2013-11-21 20:01 ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=527CF712.90809@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox