xfs
[Top] [All Lists]

Re: TAKE - userland build environment

To: Russell Cattelan <cattelan@xxxxxxxxxxx>
Subject: Re: TAKE - userland build environment
From: "Nathan Scott" <nathans@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 6 Jul 2000 09:22:50 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: Russell Cattelan <cattelan@thebarn.com> "Re: TAKE - userland build environment" (Jul 6, 8:23am)
References: <200007050139.LAA22415@snort.melbourne.sgi.com> <3963B4E0.5CD526CF@thebarn.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
mornin' Russell,

On Jul 6,  8:23am, Russell Cattelan wrote:
> Subject: Re: TAKE - userland build environment
> Nathan Scott wrote:
> 
> Tom Duffy did some rpm's for he quick usenix XFS cd.

yes (though I thought it was Ananth) - I used this as the basis
of the autoconf/configure-driven spec.

> Could you clean thing up so we don't have multiple rpm specs checked

certainly.

> into the tree. I would also be a good idea to send Tom a note and find
> out how the XFS rpm's should play with the rest of pro-pack.
> 

I understand this is a done deal - the pcp build fits into
pro-pack and we've mimicked the pcp build.  Mark knows the magic
way to make this all come together (mhist).  Also, the failsafe
folk are using a build based on the pcp mechanism that we now
use, so we're not in uncharted waters here.

I'll verify today that binary & source rpms can actually be
generated (I suspect not - since I haven't converted mkfs,
maxtrres, and xfs_repair yet), and will check something in later
today if need be (so that we have a complete package build - I
was going to leave this till I got to each of these tools for
de-SIMing, but I may as well just do the Makefiles for these
now).

> Final suggestion: since rpm's are distribution specific they probably 
> shouldn't
> be in the source
> tree directly, the SPECS dir at the top of the tree seems like a better spot.
> 

I have to disagree with this, but with good reasons ;) -

a/ anyone downloading the xfs-cmds tgz/src.rpm should be able
   to roll their own rpm (this is what the distributions will
   want to do, right?), therefore we need to provide all the
   infrastructure as part of the downloadable package;

b/ if we provide an example of how to integrate into one package
   manager (rpm), other people can use that example (this is
   exactly what happened with pcp & the debian folk who helped
   us out there);

c/ people wanting to build on other architectures will need the
   specfile integrated into the build as we have now done...
   I doubt we'll be building alpha/sparc rpms, right? - but I
   imagine others will want to... we shouldn't get in their way/
   make them reinvent the wheel.


cheers.

-- 
Nathan

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