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

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@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2013-11-08 14:56 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
2013-11-08 14:56     ` Karel Zak [this message]
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=20131108145645.GB12667@x2.net.home \
    --to=kzak@redhat.com \
    --cc=psusi@ubuntu.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