[Top] [All Lists]

Re: xfsprogs/xfsdump release process

To: Mike Frysinger <vapier@xxxxxxxxxx>
Subject: Re: xfsprogs/xfsdump release process
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 24 Feb 2009 13:44:05 -0500
Cc: xfs-oss <xfs@xxxxxxxxxxx>
In-reply-to: <200902241005.49414.vapier@xxxxxxxxxx>
References: <200902221348.51905.vapier@xxxxxxxxxx> <200902221539.26143.vapier@xxxxxxxxxx> <200902241005.49414.vapier@xxxxxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17)
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.

<Prev in Thread] Current Thread [Next in Thread>