From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2-utils: master - GFS2: Add script to create release tarball
Date: Mon, 11 Oct 2010 09:44:05 +0100 [thread overview]
Message-ID: <1286786645.2753.3.camel@dolmen> (raw)
In-Reply-To: <4CAFF7E6.1060605@redhat.com>
Hi,
On Sat, 2010-10-09 at 07:04 +0200, Fabio M. Di Nitto wrote:
> did you try to use "make dist" directly from the build tree?
>
No, and tbh I don't really want to rely on that. My little script is
simple and does the job just fine.
> based on the version/name info in configure.ac, it will do tests and
> then create the tarball release for you. The tests include build of the
> tarball, and extra checks of the build system itself.-
>
> The script you wrote would also pack .git related stuff that you don't
> want to ship in a release.
>
> Fabio
>
What stuff that I don't want is it including? I've not spotted anything
being added incorrectly,
Steve.
> On 10/08/2010 08:11 PM, Steven Whitehouse wrote:
> > Gitweb: http://git.fedorahosted.org/git/gfs2-utils.git?p=gfs2-utils.git;a=commitdiff;h=8ad7ccfab98e55b69987f8634feab9083cd86431
> > Commit: 8ad7ccfab98e55b69987f8634feab9083cd86431
> > Parent: 9fd48ba18df408b00041a0b18e60b0f0e3032e9a
> > Author: Steven Whitehouse<swhiteho@redhat.com>
> > AuthorDate: Fri Oct 8 18:43:14 2010 +0100
> > Committer: Steven Whitehouse<swhiteho@redhat.com>
> > CommitterDate: Fri Oct 8 18:43:14 2010 +0100
> >
> > GFS2: Add script to create release tarball
> >
> > Based upon the branch and current release tag, this script
> > creates a tar ball suitable for release.
> >
> > Signed-off-by: Steven Whitehouse<swhiteho@redhat.com>
> > ---
> > make-tarball.sh | 22 ++++++++++++++++++++++
> > 1 files changed, 22 insertions(+), 0 deletions(-)
> >
> > diff --git a/make-tarball.sh b/make-tarball.sh
> > new file mode 100755
> > index 0000000..71d78fe
> > --- /dev/null
> > +++ b/make-tarball.sh
> > @@ -0,0 +1,22 @@
> > +#!/bin/bash
> > +
> > +FILES=`git ls-files | sed -e's/^/gfs2-utils\//'`
> > +BRANCH=`git show-branch --current | sed -e's/.*\[//' -e's/\].*$//'`
> > +DESC=`git describe 2>/dev/null`
> > +
> > +if [ $? != 128 ]; then
> > + if [ ${BRANCH} == "master" ]; then
> > + VERSION=-${DESC}
> > + else
> > + VERSION=-${BRANCH}-${DESC}
> > + fi
> > +fi
> > +
> > +DEST=`pwd`/gfs2-utils${VERSION}.tar.gz
> > +
> > +echo "Creating ${DEST}..."
> > +
> > +(cd ..; tar -zcf ${DEST} ${FILES})
> > +
> > +echo "Done."
> > +
> > _______________________________________________
> > cluster-commits mailing list
> > cluster-commits at lists.fedorahosted.org
> > https://fedorahosted.org/mailman/listinfo/cluster-commits
>
next prev parent reply other threads:[~2010-10-11 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101008181121.E0798120296@lists.fedorahosted.org>
2010-10-09 5:04 ` [Cluster-devel] gfs2-utils: master - GFS2: Add script to create release tarball Fabio M. Di Nitto
2010-10-11 8:44 ` Steven Whitehouse [this message]
2010-10-11 15:42 ` Fabio M. Di Nitto
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=1286786645.2753.3.camel@dolmen \
--to=swhiteho@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).