Hi Thomas On Fri, 20 Sep 2002, Thomas Raschbacher wrote: > just wanted to know if someone is already working on a distutils install > (setup.py) if not i could do it... i would only need a few hints on what > can be installed in the /usr/share/python ... path and what not (afaik > there are some things that should reside elsewhere or am i wrong?)
Just my thoughts ... It's some time ago I read the distutils docs, but I could imagine that some "common" paths for some platforms are coded into distutils. So not every author of a setup script has to know of these conventions. I just looked, - see distutils.sysconfig.get_config_vars.py and distutils.sysconfig.get_config_var.py Commonly, I think, "share" directories contain stuff that is platform- independent. In other words, mounting "share" directories on computers with different architectures (e. g. Intel and Sparc) makes sense. The most common files in "share" are documentation files but Python code, since it's platform-independent, also qualifies for this directory. One exception is that platform-independent files which are used by a user from a command line, are also often put into /usr/local/bin, though the exact path can vary across platforms. In distutils, I saw the config var 'BINDIR', which is '/usr/local/bin' for my FreeBSD installation. MakeAppWorkDir.py should be (also) into this directory (which the FreeBSD port just lacks ;-) ); on Posix systems, you will have to modify the first line (#!) to reflect the path of the python binary. I don't know how to deal with Windows or even other operating systems here. However, there may be abstractions for this in distutils. Another thing are logfiles of individual app work dirs. Typically, they are stored below /var/log/something though the current Webware distribution puts them in each app work dir under `Logs`. Because some paths currently are hard-coded into the Webware files which are not in app work dirs, you would have to modify these Webware files which probably isn't merely a matter of distribution formats. ;-) A related topic are the paths for session data etc. One may consider these should also be somewhere under /var, so that "paranoid" administrators can mount /usr/local read-only. Personally, I give this point relatively low priority, YMMV. Stefan ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
