"Rezand" <[EMAIL PROTECTED]> writes: > Yet, it appears to have installed python to /usr/bin and /usr/lib. As a > result, when I try to use any of the turbogears installers, I get an > error (pasted at the end of this post) as it tries to install to the > site-packages directory under /usr/local/lib.
What makes sense since these are not packaged installations and they apply to your local machine only (hence it can't be /usr/share). > With the ez_setup.py, it's easier to get this to work by using the -d > parameter to redirect it. I don't seem to have any such easy mechanism > to remedy this using your new script installer. I prefer this kind of separation. It is also easier to see what has been installed outside of my package manager and include it on my backups or migration from development server to production server proccess. All what it took me was create /usr/local/lib/python2.4/site-packages and voi là! Everything got easier to maintain (as I said, no need to check what files in /usr/lib/python2.4/site-packages belong to some RPM and what were hand installed) :-) This was a recent change in SuSE. It wasn't like that a while ago, so I believe this is some compilation option for Python. As you have the source you can change that, generate new python packages and have your "easy_install"ed packages put on the same place as RPM packages without passing any option (you could also make an alias to easy_install passing the "-d" option making it transparent for you...). Be seeing you, -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
