if you have anything that details your rpm deployment
workflow at mozilla, i'd love to see it.
I
work in a very active build environment, and
repetitive"setup.py build" time is pain point.
currently,
we have a pretty fragile virtualenv caching strategy, and I've
even considered patching distutils so that "setup.py build"
would somehow work against a cache.
currently,
my mindset is to migrate to a modular rpm install strategy
(managed by puppet) to prevent wasteful build time.
P.S.
Daniel's "wheel" format is another possible to answer to my
concern