Hey thanks Phillip. This will make updating of the package very easy over the long term.
I was already thinking that it would be best to keep support for the eggs in packaged system as once installed, end users will likely want to update their system without re-downloading and re-installing the whole thing all over again. Basically this will just work like a non-root install for all the packages. Or at least, that is how I am envisioning it. (And providing I even go ahead with this.) Thanks again. This will help. :-) Krys Phillip J. Eby wrote: > Krys Wilken wrote: > >>I've been mulling over the idea of an all-in-one >>Python+TG+SQLlite+PostgresSQL+Apache windows installer (a la Plone). It >>could contain a self-contained python with all the necessary >>site-packages to run TG and a directory structure for TG-based apps. >> >>At my work, our net connection is heavily >>firewalled/proxied/content-filtered and auto-downloading anything just >>does not work. I have to get TG in what amounts to basically a >>connectionless system. >> >>I am thinking that this kind of all-in-one setup.exe might be useful. > > > FYI, to create it, you can simply use easy_install with the -d option > to specify a target directory, and leave off the --script-dir bit, > adding --exclude-scripts and --always-copy so it won't generate scripts > and will copy all the needed eggs to your target directory. This will > dump all the eggs in a single directory for you, at which point you can > package them up along with ez_setup.py and the setuptools egg. As long > as the setuptools egg is in the same directory with ez_setup.py, the > resulting directory can be shipped anywhere for installation (assuming > the same platform, of course). On the destination system, replace the > TurboGears URL in the -f option with the name of the current directory, > e.g.: > > ez_setup.py -f . --script-dir=wherever TurboGears > > and then the install process will pull all its eggs from the current > directory. > > Anyway, you can wrap all that in some kind of setup facility if you > want, I'm just giving you what will be the most robust process, because > it won't require you to hardcode anything about what scripts there are > or what eggs are needed. If Kevin changes anything, you'll pick that > up when you run easy_install to build the egg directory that will be > wrapped by your setup process. > >
