[PyVault-devel] Re: package name for mod_python (Re: introduction)

[Jeff Pitman]

On Saturday 12 February 2005 22:37, Terrel Shumway wrote:
> > Anyway, it might be overkill, but i just
> > wanted to learn how cheetah worked.
>
> Cheetah is one of my favorite tools, but it is overkill for this.  I
> think a better approach is to create a bdist_rpm subclass that
> overrides _make_spec_file. I have one that I started creating before
> I found pyvault.  I'll take a look at the spec file template,
> finish/update my class, and post it.
>
> (If we can get it blessed by the BDFLs of Distutils, it will make
> *everyone's* life easier, since all rpms will be pyvault-compatible
> by default.)

I look forward to your distutils->spec generator thingy!  I'll drop the 
template once I import the other in.  Then we'll have to document it on 
the wiki.

My --rpm-record patch would make things easier too:

http://sourceforge.net/tracker/index.php?func=detail&aid=1035576&group_id=5470&atid=305470

I've implemented it as a patch against py2.3 and py2.4 in pyvault to aid 
in pyvault spec builds.  So far, the experiment has worked out well.

> > I'll be putting together a hacking document soon which will talk
> > about how to setup a build chroot, etc. It'll also mention the
> > "alternatives" package and how to use it.
>
> In the hacking document, you might also mention what `mach` is,
> where to get it, and why you would need it. 

It's a wiki! ;-)

> Also, say what a 
> "large partion" means: 8GB or 80GB?

I'm looking at 1.5GB per chroot with py1.5, py2.2, py2.3, py2.4 built in 
each.  So, that includes minimum build environment with the source 
trees, source rpms, bin rpms, and build directories for each of the 
above four packages.  Other packages beyond these are not as large, so 
maybe a padded 2GB per chroot is a good estimate.

Also, I could put mach in an optional area.  Because, technically specs 
are just specs and you can make them work in whatever environment you 
want.  Mach has some neat things, but has some weaknesses.  The 
greatest being lost interest by upstream authors.  Something else may 
be in the works.  But, this is all incremental anyway.  So, not a big 
deal.  I'll mull about the ultimate build system later on.

take care,
-- 
-jeff