xfs
[Top] [All Lists]

Re: xfsprogs/xfsdump release process

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: xfsprogs/xfsdump release process
From: Mike Frysinger <vapier@xxxxxxxxxx>
Date: Tue, 24 Feb 2009 14:06:23 -0500
Cc: "xfs-oss" <xfs@xxxxxxxxxxx>
In-reply-to: <20090224184405.GB28007@xxxxxxxxxxxxx>
Organization: wh0rd.org
References: <200902221348.51905.vapier@xxxxxxxxxx> <200902241005.49414.vapier@xxxxxxxxxx> <20090224184405.GB28007@xxxxxxxxxxxxx>
User-agent: KMail/1.11.0 (Linux/2.6.28; KDE/4.2.0; x86_64; ; )
On Tuesday 24 February 2009 13:44:05 Christoph Hellwig wrote:
> 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.

ok, as long as the tarball has a configure script :)
-mike

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