Thanks to everyone who responded. I only had time to partially test the first method for my uses. As i go through these I'll likely have some questions.
Thanks again Corey On Sun, Feb 14, 2010 at 4:26 AM, Mike C. Fletcher <[email protected]>wrote: > Corey Kovacs wrote: > > Folks, > > > > I've been trying to find a reliable and repeatable way to get TG2 > > installed offline using several > > different methods. The methods I have tried are somewhat inconsistent > > in terms if success rate. > > > > Every time I do an install I am required to manually build and install > > several items that don't get > > resolved as dependencies. > > > > I have of course seen the methods referred to in the online docs and > > the basic 'easy_install -f . TurboGears2' > > With the recent version of software in the "current" release, it > > doesn't work as the version of ToscaWidgets isn't > > recent enough. > > > > My question is simple. If there is a good way of doing this already, > > then someone please let me know what it is. > I use a little hack-script I wrote that skims the output of easy_install > and re-downloads the reported downloads (yes, that's incredibly > wasteful, but it was a quick hack). Usage looks like this: > > mcfle...@sturm:~/tg-dev$ mkdir recordeggs-sample > mcfle...@sturm:~/tg-dev$ cd recordeggs-sample/ > mcfle...@sturm:~/tg-dev/recordeggs-sample$ mkdir sources > mcfle...@sturm:~/tg-dev/recordeggs-sample$ virtualenv --no-site-packages > sample > New python executable in > sample/bin/python > Installing > setuptools............done. > mcfle...@sturm:~/tg-dev/recordeggs-sample$ cd > sample/ > mcfle...@sturm:~/tg-dev/recordeggs-sample/sample$ source > bin/activate > (sample)mcfle...@sturm:~/tg-dev/recordeggs-sample/sample$ easy_install > -U setuptools recordeggs > ... > (sample)mcfle...@sturm:~/tg-dev/recordeggs-sample/sample$ recordeggs -r > ../sources/ -i http://www.turbogears.org/2.1/downloads/current/index > tg.devtools > (sample)mcfle...@sturm:~/tg-dev/recordeggs-sample/sample$ paster > quickstart sample > ... > (sample)mcfle...@sturm:~/tg-dev/recordeggs-sample/sample$ recordeggs -r > ../sources/ -i http://www.turbogears.org/2.1/downloads/current/index > ./sample > ... > (sample)mcfle...@sturm:~/tg-dev/recordeggs-sample/sample$ deactivate > mcfle...@sturm:~/tg-dev/recordeggs-sample/sample$ cd .. > mcfle...@sturm:~/tg-dev/recordeggs-sample$ virtualenv --no-site-packages > sample2 > New python executable in sample2/bin/python > Installing setuptools............done. > mcfle...@sturm:~/tg-dev/recordeggs-sample$ cd > sample2/ > mcfle...@sturm:~/tg-dev/recordeggs-sample/sample2$ source > bin/activate > (sample2)mcfle...@sturm:~/tg-dev/recordeggs-sample/sample2$ easy_install > -U setuptools recordeggs > ... > (sample2)mcfle...@sturm:~/tg-dev/recordeggs-sample/sample2$ recordeggs > -p ../sources/ > ... > > that creates a directory ../sources which has a recipe that lists all of > the packages which were installed. The -p invocation installs all of > those packages. Normally after the initial setup I check in the sources > directory and then just manually add/remove items from the > sources/playbackeggs.list file. It's nowhere near as elegant as PIP or > the like, but I find it works for my TG projects pretty well. Note that > the setup for the quickstarted project actually installs packages which > aren't considered dependencies, but are used by the quickstarted > application. I normally create a "throw-away" project and install it as > shown above to pull in those packages. > > HTH, > Mike > > -- > ________________________________________________ > Mike C. Fletcher > Designer, VR Plumber, Coder > http://www.vrplumber.com > http://blog.vrplumber.com > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<turbogears%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/turbogears?hl=en. > > -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
