From: Christoph Hellwig <hch@infradead.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfsprogs/xfsdump release process
Date: Tue, 24 Feb 2009 13:44:05 -0500 [thread overview]
Message-ID: <20090224184405.GB28007@infradead.org> (raw)
In-Reply-To: <200902241005.49414.vapier@gentoo.org>
On Tue, Feb 24, 2009 at 10:05:48AM -0500, Mike Frysinger wrote:
> On Sunday 22 February 2009 15:39:25 Mike Frysinger wrote:
> > On Sunday 22 February 2009 13:48:49 Mike Frysinger wrote:
> > > how are release tarballs created ? seems like there's an error in the
> > > process as the dmapi-2.2.9 contains files it shouldnt. for example,
> > > autom4te.cache/, include/builddefs, etc...
> >
> > in a similar vain, every xfsdump/xfsprogs release has made people run
> > `autoconf` first as the configure script is considered part of the
> > distclean target in general. i dont think that makes any sense as the
> > configure script should be included with every release tarball.
>
> so how are release tarballs made ? i dont see a "dist" target or anything ...
The current ones were made using a hacked up release script form me.
There's a Makepkgs script in the tarballs that generates better
tarballs, but knowledge about it was lost in various transitions and
it started to bitrot. I'm fixing it up so we can use it for the next
release right now.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-24 18:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 18:48 dmapi-2.2.9 release Mike Frysinger
2009-02-22 20:39 ` xfsprogs/xfsdump release process Mike Frysinger
2009-02-23 5:00 ` Felix Blyakher
2009-02-23 7:22 ` Christoph Hellwig
2009-02-23 16:10 ` Felix Blyakher
2009-02-23 16:25 ` Mike Frysinger
2009-02-23 16:38 ` Felix Blyakher
2009-02-23 19:29 ` Eric Sandeen
2009-02-24 13:20 ` Christoph Hellwig
2009-02-24 15:05 ` Mike Frysinger
2009-02-24 18:44 ` Christoph Hellwig [this message]
2009-02-24 19:06 ` 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=20090224184405.GB28007@infradead.org \
--to=hch@infradead.org \
--cc=vapier@gentoo.org \
--cc=xfs@oss.sgi.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