-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
Wichert Akkerman wrote:
Previously Chris Withers wrote:
Tres Seaver wrote:
> KGS the > concept is very easy to implement; you just make available on some URL a > buildout versions.cfg, or you run your own package index. OK, the former I can see happening on an end-user project, the latter is just too much work. Not really. Collect the tarballs, run a script, configure Apache to serve that diretory. Hmm, too much... but is it needed? Can you not point index at just a local folder on disk? I'm sure the Plone folks did something like this, maybe Hanno can chime in? What we do is: collect the tarballs, serve the resulting directory. I have not seen a need to run a script.
How do you collect the tarballs?
I dig them out of wherever I told whatver tool (buildout, compoze fetch, etc) to put them.
How do you serve the resulting directory?
See above. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ3JKI+gerLs4ltQ4RAtZ8AJoCjuoGAdIeHBd+A/16jms+U+ItGgCdEA6d MAm43IFFskpvj8sANIPGvwA= =P5rk -----END PGP SIGNATURE-----