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

[Terrel Shumway]

> If apache 1.x is a dead-end, then having pythonXY-mod_python appears to
> be the candidate package name.

I agree. I have no plans to use or package the pre-3.0 mod_python

My guess is that the people who care about using python and mod_python 
tend to be the same people who started running apache 2 a long time 
ago. (Non-evangelists will be using PHP or ASP. :-P  )

> I like to use it after running a quick "python setup.py bdist_rpm",
> which produces a .spec file.  

BTW: you can also say "python setup.py bdist_rpm --spec-only"

The .spec file created by bdist_rpm is pretty simple, but if you look at 
the code (`_make_spec_file`)  you'll see that it has access to some 
setup-time info that is tedious to reproduce outside the distutils 
framework (e.g. dist.has_scripts() and dist.has_ext_modules()).

> 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'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. Also, say what a 
"large partion" means: 8GB or 80GB?