[Distutils] nailed-down versions by having custom index
Reinout van Rees
reinout at vanrees.org
Wed Feb 3 11:22:15 CET 2010
On 02/02/2010 10:25 PM, Tres Seaver wrote:
>> But how to get the right collection of tarballs in there? Is that a
>> by-hand approach? Can you automate it?
> You might look at compoze: it is designed to allow fetching sources and
> building an index based on the current workingset:
Thanks, I'll try that one out. He he, a README in structuredtext (not
reST) format if I'm not mistaken. I still like that format :-)
>> Question 2: I thought you could only have one index. So installing
>> something extra from pypi seems out. How do people handle that?
> Fetch it from pypi and put it in your index.
My fear is that I end up with quite a lot of project-specific custom
indexes if I want to keep it rebuildable. Multiply that with a quite a
number of project releases (so: new indexes) and you're looking at a big
bucket of bits.
How's that working out in practice for you?
If you have a base "product/framework/whatever" (a bunch of libraries,
partly your own and partly from pypi), I can see it is useful to have
that in such a custom index. But multiple in-house websites will use
that *and* add their own extra needed libraries to the mix.
=> So you need to add a new index for that, duplicating the
"product/framework/whatever" release and adding your own extra eggs?
Reinout van Rees - reinout at vanrees.org - http://reinout.vanrees.org
Programmer/advisor at http://www.nelen-schuurmans.nl
"Military engineers build missiles. Civil engineers build targets"
More information about the Distutils-SIG