The argument was --script-dir, but yes that worked just fine. Thanks for the hint!
Keith Kevin Dangoor wrote: > I believe that the new tgsetup.py defaults to installing scripts in > /usr/local/bin... does "tgsetup.py --install-scripts your-bin-dir" > work for you? > > Kevin > > On Nov 29, 2006, at 10:43 AM, Keith R. Fieldhouse wrote: > >> >> I run TurboGears on an Ubuntu (Dapper) box, using a virtual-python.py >> created root. This works out quite well for me. I noted last night >> that while the tgsetup.py from 1.0b1 works just fine within my root, the >> tgpython.py from 1.0b2 fails. It seems to be insisting that it be able >> to install into /usr/bin (which it can't since I'm not running with root >> privs). I didn't have a chance to try and debug this but I thought I'd >> report the behavior in case it's just an "oops" of some sort. >> >> I did start from scratch a couple of times to make sure I hadn't missed >> a step (like forgetting to set my PATH or whatnot), but the results were >> the same: 1.0b1 tgsetup.py works fine, 1.0b2 tgsetup.py does not. Of >> course it's still possible I'm doing something silly, but I don't think >> so... >> >> Keith >> >> Kevin Dangoor wrote: >>> Sorry about the delay. I was out of town most of last week. >>> >>> I've fixed the bind_meta_data problem and the tgsetup.py on Windows >>> problems. Please give it a try and if all is good, I'll tag it. >>> >>> My next step after that is to go through all of the 1.0b2 tickets in >>> trac (paying particular attention to any patches in there) and decide >>> which get applied. I'm going to move tickets around as needed to meet >>> this goal: >>> >>> 1) get outstanding patches applied or rejected (or at least commented >>> on, if changes are needed) >>> 2) get a 1.0b3 out with that >>> 3) see if there are bugs that absolutely must get fixed and work on >>> fixing those >>> 4) release a 1.0b4 with those fixes >>> 5) 1.0rc1 if 1.0b4 is not broken >>> 6) 1.0 final >>> >>> After that, we can schedule tickets for 1.0.1, etc. I just don't like >>> making release candidates of betas. >>> >>> It also occurs to me that tgsetup.py can request a specific version of >>> TurboGears, which means that one version of tgsetup can download the >>> current release, the next one coming up, a nightly build, whatever... >>> we can do some useful things with that. >>> >>> Kevin >>> >>> -- >>> Kevin Dangoor >>> TurboGears / Zesty News >>> >>> email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >>> company: http://www.BlazingThings.com >>> blog: http://www.BlueSkyOnMars.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] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
