On Thu, Apr 9, 2009 at 11:37 AM, Iain Duncan <[email protected]> wrote:
>> Regardless of what the problem is, in the future it would be nice if >> we provided an 'all in one' install archive. Like a pip bundle (but >> then we have to require pip), or I think zc.sourcerelease can produce >> something similar. EggFreezer also does something along these lines >> but was more of a binary distribution installer. >> >> Something that bootstraps itself and installs everything without >> having to go through pypi, like a fully self contained go-pylons.py > > +1 on that! There are a few ways to go with this. - A tarball containing all the source packages and an installation script. - Include everything in the script. appengine-homedir does this; e.g., base64-encoding site.py and putting it in a string. But that would not be feasable for entire packages or large files; the file would be impossible to edit if you have to go through pagefuls of base64-encoded text. - A tarball containing preinstalled site-packages files. These may need to be different per platform or Python version. - Can all of Pylons and its dependencies be zipped now? If not, which ones can be? Our goal should be a zip of everything except the simplejson speedups, even if we don't install it zipped by default. - App Engine needs some alternative versions. * Full Pylons without .pyc or simplejson speedups. * Same but zipped, or zipped per package. * Exclude obsolete webhelpers etc. * Exclude nose, tests, pip, admin utilities, the non-pkg_resources part of Setuptools, and other things not used on the server. * Other variations to limit the number of files and size. App Engine is easier because there's only one Python version (2.5.2) and no platform-specific code (since C modules can't run on the server). Regular webservers may need more variations due to the different Python versions, platforms, and people's notions of what they need. On the other hand, regular webservers not have the severe restriction on number of files, so people are less concerned about installing unused packages. appengine-homedir provides a nice directory structure for organizing a Pylons application inside a virtualenv. Maybe we should support that in other environments? On the other hand, I like keeping my virtualenvs separate from my applications, so I can run the same application under different virtualenvs. So to reiterate, the main goals seem to be: - An installation archive that does not require PyPI or network access. - A script like go-pylons.py for use therewith. - Enough flexibility so that we can build upgrades and alternative versions without a lot of time and effort. - An archive containing either source packages or installed packages, whichever seems most feasable. - Various pip features like requirements, bundle, egg cache may help. Also, all Pylons dependencies are maintained at http://pylonshq.com/download . (However, that page includes more than we need, specifically old versions.) - Integration with Virtualenv. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
