[Zope-dev] Clarification regarding acl_user
Hi I am finding problem in controlling the user list in open flow. Hoe to access the acl_user folder placed in the root directory from a sub directory. I have a code which fetches me the user present in the same directory. But I need to access the user present in the acl_user folder in the root directory. I am using a user account which is created in the root directory . Hence i assume that i have the permission to access the contents of acl_user folder in the root directory. looking forward for a quick reply. Harish. SMS using the Yahoo! Messenger; Download latest version.
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
- Original Message - From: Adrian van den Dries [EMAIL PROTECTED] May I respectfully ask why there is so much concern with such complicated setups? Surely a production environment (which is what any Zope distribution should aim for) will standardise on a software version? I have this need - and what we do is *exactly* what you ask: we standardise on a software version, on service level. It seems (my impression) that most unix distros take the following view: one service, one machine. We often find that we need to run several versions of both Zope and Apache on the same machine at the same time; this might be because the current production version of a service needs to have some packages for apache/zope that conflict with newer versions of apache/zope, or simply because we do not want to change the environment for production services that work. I have created a buch of shell scripts that allows me to handle several versions of python and Zope on the same machine, as well as manage several INSTANCE_HOMEs. Each INSTANCE_HOME can specify which python to use, which zope to use and any extra stuff that is needed (like what Oracle envrionment it wants to run with, etc). I will have/have had to change these for both Zope 2.6 and for Zope 2.7 - but my hope is that with 2.7 I can just throw my scripts away and use the stock ones. If the concern is because *developers* want to run multiple Zope instances on multiple Zope versions with multiple Python versions, then I would suggest writing an *alternative* mechanism for developers to mangle their PYTHONPATHs and whatever. I find that solutions for production environments, in the style of the one oulined above, work very well for development environments as well. My 2 öre worth... /dario - Dario Lopez-Kästen, IT Systems Services Chalmers University of Tech. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
Chris wrote: We have make-driven software that creates us a tree via a single command by checking out various version of Python, Zope, etc. from CVS and compiling and installing them. Different versions of Zope and Python, etc. can be installed in opt and we use symlinks to manage versioning. Could that make-driven software be made public? I'm currently trying to create similar Makefiles (for a new FreeBSD zope port) and would be interested in using ZC files. How do those files compare to the buildscript: http://cvs.zope.org/NZO_SiteLayout/buildout_zope_sandbox?cvsroot=Zope.org PieterB ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] os.system problem
Ensure that the binaries being called through os.system() are in the program search path. -aj P.S. Use the zope mailinglist next time --On Donnerstag, 19. Juni 2003 12:12 Uhr +0200 Arjan Huizer [EMAIL PROTECTED] wrote: Hi, I have created an external method that is called when I upload a file. This external method will execute the validate_file function from my python file in the Extensions directory. The script creates a file and tries to see if it contains a virus. It does run, but after creating the file, the os.system and os.remove commands do not seem to do anything. When I copy the relevant code from the script to a python file and run it on the server directly, the code works. Does anyone know what could be wrong? Thanks in advance! p.s. I am running Zope 2.6.1 with CMF 1.3 on a Linux box. = import os def validate_file(file): ''' Check is file contains a virus. ''' filename = /usr/local/Zope/temp/temp.bin # Write the file to the local filesystem temp = open(filename, wb) temp.write(file.read()) temp.flush # Call virus checker error_level = os.system(f-prot + filename) # Delete temp file os.remove(filename) return error_level; ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On June 19, PieterB wrote: Could that make-driven software be made public? I'm currently trying to create similar Makefiles (for a new FreeBSD zope port) and would be interested in using ZC files. This sort of stuff is almost definitely deployment-specific (and quite likely ZC proprietary property - that is much of their revenue!) How do those files compare to the buildscript: http://cvs.zope.org/NZO_SiteLayout/buildout_zope_sandbox?cvsroot=Zope.org Jeebers, someone sure has an aversion to shell functions! ;-) a. -- Adrian van den Dries [EMAIL PROTECTED] Development team www.dev.flow.com.au FLOW Communications Pty. Ltd. www.flow.com.au ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Thu, Jun 19, 2003 at 09:26:51AM +1000, Adrian van den Dries wrote: Well, if you're going to have a policy shoot-out: [...] I think most of us would agree that .py(c) files are *libraries* and not *data files*. Data files would be the skeleton instance directory. Of course i do not agree, and your vision of those documents is quite erroneous, but this is an off-topic issue so i won't discusse it here. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG=[EMAIL PROTECTED] | don't depend on the language. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Hi, new to zope
Hi everybody, I am new to Zope (and a little experienced with Python). I have been trying to install already for 3 weeks the ZMySQLA... at this point I am very frustrated. I am getting the error ImportError: no module named _mysql !!! my system has Redhat 7.3 zope 2.6.1 python 2.1.3 is the python version Zope is running Mysql 3.22.32 mysql-python 0.9.2 ZMySQLA -2.0.8 I have all the -devel package installed (Mysql-devel, etc) I have installed this database connector and worked with before, but it was using windows, I didn't find any problem installing it. Now I want to get serious with Zope and therefore I am using Linux, can anyone help me on this task? Does anyone know what am I doing wrong? I would also appreciate if somebody could give me an up to date list of things to have and to do on installing that zope object Thaansk Rezuma ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Hi, new to zope
--On Donnerstag, 19. Juni 2003 9:33 Uhr -0400 Ramon Linan [EMAIL PROTECTED] wrote: Hi everybody, I am new to Zope (and a little experienced with Python). I have been trying to install already for 3 weeks the ZMySQLA... at this point I am very frustrated. I am getting the error ImportError: no module named _mysql !!! This is a problem of your PYTHONPATH! Python can not find the module and is unable to import it. The simplest solution is to point PYTHONPATH to the directory where the _mysql.so binary is installed! -aj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Wed, Jun 18, 2003 at 03:08:12PM -0400, Chris McDonough wrote: If you want to change your Zope controller to work with 2.7, I think you'll either be very happy (or very disappointed, seeing how much work you put in to creating your own config files) to know that Zope 2.7+ instances have their own configuration file which has a syntax patterned after an Apache configuration file; the parsing system uses the ZConfig package (http://www.zope.org/Members/fdrake/zconfig/). I have attached the zope.conf.in file that represents a valid Zope instance configuration file. I'm both disappointed and happy for the same reason :) When 2.7 will be out i'll adapt my zopectl to the new Zope installation procedure. As an upshot, z2.py no longer exists and the zopectl that runs Zope [...] That's not big deal: I'll manage instance operation trough instance specific zopectl script. I'd love to see your zopectl system work with Zope 2.7, and though I [...] If you want it to support Zope 2.7, I'd be happy to answer any questions about the new installation/startup process. I'll keep it a separate package, and i surely take advantage of your help. In particular, I think you'd need to change your zopectl conf file. [...] I'll most probably do in this way. Support for installing docs to a specific directory is no big deal. I'll add it to the Zope 2.7 TODO. Sounds cool. I'd advise against installing Zope library files into site-packages unless you put them in a site-packages subdirectory (like site-packages/zope270 or site-packages/zope271). I'll keep this in mind. If you can provide specific direction on how to make the Zope source tarball installer service your goals better, I'll be happy to try to implement any suggestions given that it makes sense in the larger cross-platform context. I'll mail you privately for this. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG=[EMAIL PROTECTED] | don't depend on the language. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Thu, 2003-06-19 at 02:57, PieterB wrote: Chris wrote: We have make-driven software that creates us a tree via a single command by checking out various version of Python, Zope, etc. from CVS and compiling and installing them. Different versions of Zope and Python, etc. can be installed in opt and we use symlinks to manage versioning. Could that make-driven software be made public? I'm currently trying to create similar Makefiles (for a new FreeBSD zope port) and would be interested in using ZC files. How do those files compare to the buildscript: http://cvs.zope.org/NZO_SiteLayout/buildout_zope_sandbox?cvsroot=Zope.org The NZO make-driven buildout is an early revision of what we use. There is no publically available later revision, but it hasn't changed all that much. HTH, - C ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Thu, 2003-06-19 at 10:14, Chris McDonough wrote: On Thu, 2003-06-19 at 02:57, PieterB wrote: Chris wrote: We have make-driven software that creates us a tree via a single command by checking out various version of Python, Zope, etc. from CVS and compiling and installing them. Different versions of Zope and Python, etc. can be installed in opt and we use symlinks to manage versioning. Could that make-driven software be made public? I'm currently trying to create similar Makefiles (for a new FreeBSD zope port) and would be interested in using ZC files. How do those files compare to the buildscript: http://cvs.zope.org/NZO_SiteLayout/buildout_zope_sandbox?cvsroot=Zope.org The NZO make-driven buildout is an early revision of what we use. There is no publically available later revision, but it hasn't changed all that much. Scratch that! I hadn't looked at it in a while. This looks nothing whatsoever like what our Makefile-driven buildout for NZO used to look like. I guess Sidnei didn't like it and changed it to a shell-driven buildout. The old version should be floating around somewhere... ah, there is is: http://cvs.zope.org/SiteLayout/?cvsroot=Zope.org. - C HTH, - C ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Hi, new to zope
Thanks aj for your quick answer... the situation is this, I though that was a problem with the path too so, yesterday I did export PYTHONPATH=/usr/local/lib/python2.1/site-packages/ there is one of the 3 places that I have that library, bit I still get the same error. I tried something desperate and put a symbolic link to that path (ln -s /usr/local/lib/python2.1/site-packages/_mysql.so) and then the error was _mysql failed init ... !!! don't know what else to do -Original Message- From: Andreas Jung [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 9:35 AM To: Ramon Linan; [EMAIL PROTECTED] Subject: Re: [Zope-dev] Hi, new to zope --On Donnerstag, 19. Juni 2003 9:33 Uhr -0400 Ramon Linan [EMAIL PROTECTED] wrote: Hi everybody, I am new to Zope (and a little experienced with Python). I have been trying to install already for 3 weeks the ZMySQLA... at this point I am very frustrated. I am getting the error ImportError: no module named _mysql !!! This is a problem of your PYTHONPATH! Python can not find the module and is unable to import it. The simplest solution is to point PYTHONPATH to the directory where the _mysql.so binary is installed! -aj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Hi, new to zope
add the following to your z2.py: import sys print sys.path Check the output against your PYTHONPATH. -aj --On Donnerstag, 19. Juni 2003 10:41 Uhr -0400 Ramon Linan [EMAIL PROTECTED] wrote: Thanks aj for your quick answer... the situation is this, I though that was a problem with the path too so, yesterday I did export PYTHONPATH=/usr/local/lib/python2.1/site-packages/ there is one of the 3 places that I have that library, bit I still get the same error. I tried something desperate and put a symbolic link to that path (ln -s /usr/local/lib/python2.1/site-packages/_mysql.so) and then the error was _mysql failed init ... !!! don't know what else to do -Original Message- From: Andreas Jung [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 9:35 AM To: Ramon Linan; [EMAIL PROTECTED] Subject: Re: [Zope-dev] Hi, new to zope --On Donnerstag, 19. Juni 2003 9:33 Uhr -0400 Ramon Linan [EMAIL PROTECTED] wrote: Hi everybody, I am new to Zope (and a little experienced with Python). I have been trying to install already for 3 weeks the ZMySQLA... at this point I am very frustrated. I am getting the error ImportError: no module named _mysql !!! This is a problem of your PYTHONPATH! Python can not find the module and is unable to import it. The simplest solution is to point PYTHONPATH to the directory where the _mysql.so binary is installed! -aj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Hi, new to zope
And maybe check the filepermissions of your _mysql.so file! It must be readable by python! -aj --On Donnerstag, 19. Juni 2003 16:41 Uhr +0200 Andreas Jung [EMAIL PROTECTED] wrote: add the following to your z2.py: import sys print sys.path Check the output against your PYTHONPATH. -aj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Wed, 2003-06-18 at 23:13, Adrian van den Dries wrote: Distribution install - most common:: ./configure.py --prefix=/usr \ --skel=/usr/share/zope/skel \ --doc=/usr/share/zope/doc mkzopeinstance.py /var/lib/zope/default ln -s /var/lib/zope/default/etc /etc/zope/default echo -e '[default]\n/var/lib/zope/default' /etc/zopectl.conf I think you are suggesting that all Zope config files be put into /etc/zope with a master zope config file at /etc/zopectl.conf. If so, I think this might make a lot of sense for a managed-binary Zope multi-instance controller, but this is more a function of Luca's framework than the Zope source installer. I consider my job done after someone runs mkzopeinstance. zopectl.py start default All the above is invoked by ``apt-get install zope``, and the package can use a /etc/init.d/zope to loop through all instances. This looks like it's a function of Luca's 'zopectl'; not ZC's, but given that it sounds reasonable to me. Multiple pythons, zopes, instances - most complex:: cd Zope-2.7.1 python2.1 configure.py --prefix=/opt/zope271-python21 (FWIW, configure is a shell script.) # ... python2.1 configure.py clean python2.2 configure.py --prefix=/opt/zope271-python22 # ... cd ../Zope-2.7.2 python2.1 configure.py --prefix=/opt/zope272-python21 # ... python2.2 configure.py clean python2.2 configure.py --prefix=/opt/zope272-python22 Then you permute these with: python2.1 /opt/zope271-python21/bin/mkzopeinstance.py \ /var/zope/zope271-python21-instance1 python2.2 /opt/zope271-python22/bin/mkzopeinstance.py \ /var/zope/zope271-python22-instance1 # etc. And you have an installation with all permutations of multiple Pythons, multiple Zopes and multiple instances. Are you implying that the stuff that currently goes into software_home/lib/python would be installed to the site-package directory of the Python that was used to invoke the installer? If so, the subsequent invocations above of: cd Zope-2.7.1 python2.1 configure.py --prefix=/opt/zope271-python21 make; make install cd ../Zope-2.7.2 python2.1 configure.py --prefix=/opt/zope272-python21 make; make install ... would cause the Zope 2.7.1 libraries to be stomped by the Zope 2.7.2 libraries. Does this alleviate your concerns? ;-) If you mean that the libraries are installed into /opt/zope27X-python21/lib/python, there's no problem and nothing about the installer needs to be changed. So, in any case, given that the ZC source tarball installer will not attempt to manage multiple instances (we'll leave that to Luca) here are the requirements I've gathered so far: - Add a --doc flag to configure - Add a --skel flag to configure (is this a common pattern?) Possibly: - Make it possible to install Zope libraries into the site-packages directory of the Python that invokes Zope's setup.py instead of into software_home/lib/python. Am I missing anything? - C a. -- Adrian van den Dries [EMAIL PROTECTED] Development team www.dev.flow.com.au FLOW Communications Pty. Ltd. www.flow.com.au ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
Chris McDonough wrote: On Thu, 2003-06-19 at 10:14, Chris McDonough wrote: On Thu, 2003-06-19 at 02:57, PieterB wrote: How do those files compare to the buildscript: http://cvs.zope.org/NZO_SiteLayout/buildout_zope_sandbox?cvsroot=Zope.org The NZO make-driven buildout is an early revision of what we use. There is no publically available later revision, but it hasn't changed all that much. Scratch that! I hadn't looked at it in a while. This looks nothing whatsoever like what our Makefile-driven buildout for NZO used to look like. I guess Sidnei didn't like it and changed it to a shell-driven buildout. I don't blame him. Makefiles are very obtuse--especially if you try to make them modular and reusable! FWIW, I've put together a tool for managing rollouts of many software packages at once and I'm using it quite successfully for a customer project. I'd really like to either: - Release it as open source so others can use it and help maintain it. - Replace it with something with at least the same simple UI with its functionality, maintainability, and freedom. I prefer the second option, but I've had trouble finding anything that does the right things with a simple command-line UI. RedHat's RPM doesn't do enough. Debian's apt has a nasty UI and is tied too closely with Debian. Mandrake's urpmi, equivalent to apt, is tied too closely with Mandrake. There are various commercial tools, but I despise the possibility of legal issues. Just last night, though, I noticed that Gentoo is making a Mac OS X port. Not a PowerPC port, mind you, but a port to a different OS. That means Gentoo, like Debian, is not tied directly with Linux. And Gentoo's build system is written in Python, AFAIK. Has anyone tried extracting Gentoo's build system and using it for partial software distributions? That might be the way to go. Shane ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Thu, 2003-06-19 at 09:53, Luca - De Whiskey's - De Vitis wrote: On Wed, Jun 18, 2003 at 03:08:12PM -0400, Chris McDonough wrote: I'm both disappointed and happy for the same reason :) When 2.7 will be out i'll adapt my zopectl to the new Zope installation procedure. Great. I'll keep it a separate package, and i surely take advantage of your help. Excellent. Thanks again, - C ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
--On Thursday, June 19, 2003 10:07:52 +1000 Adrian van den Dries [EMAIL PROTECTED] wrote: I'd advise against installing Zope library files into site-packages unless you put them in a site-packages subdirectory (like site-packages/zope270 or site-packages/zope271). Otherwise there will be no way to run multiple Zope versions on the same machine sanely because different Zope versions have different libraries. May I respectfully ask why there is so much concern with such complicated setups? Surely a production environment (which is what any Zope distribution should aim for) will standardise on a software version? One word: migration As I've found out the hard way, there are times when it is much easier to conduct server upgrades if you can have different versions of Zope installed on a server at the same time. This is especially true in budget constrained colocation environments where adding additional machine for the upgrade would cost money. Dan Pierson ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zpt z-sql?
What would be the syntax to call a z-sql (passing one or more parameters) from a zpt? The z-sql would retrieve a single row. Fields from this row to be shown in the zpt. I moved this over to [EMAIL PROTECTED] This list is development *of* Zope, rather than *with* Zope. --jcc ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
There's only one possible way! A-A-P! (A good match for Ape, Shane ;) It's a replacement for make by Bram Moolenaar, the author of Vim, and it looks like it does a lot of things Right. http://www.a-a-p.org/index.html In fact, Aap would fit very well with Gentoo. Gentoo's emerge system takes care of package metadata, fetching the source, and unpacking it. Once it's unpacked, it gets compiled, usually with the standard .configure; make; make install steps. Individual packages could use aap instead of make. Actually, Aap also takes care of the fetching phase. Then Gentoo installs the compiled package, keeping track of what files went where, so that they can be uninstalled, and queried for what package they belong to. This Aap doesn't do, AFAIK. -- Jean Jordaan http://www.upfrontsystems.co.za ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Thursday 19 June 2003 15:58, Shane Hathaway wrote: Has anyone tried extracting Gentoo's build system and using it for partial software distributions? That might be the way to go. I am now using Gentoo on all my servers and on this workstation. I find value in being able to manage Zope stuff as a non-root user. Portage was designed to allow this, but I doubt it is well exercised. Trying this has been on my to-do list for a while. -- Toby Dickenson http://www.geminidataloggers.com/people/tdickenson ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
Jean Jordaan wrote: There's only one possible way! A-A-P! (A good match for Ape, Shane ;) It's a replacement for make by Bram Moolenaar, the author of Vim, and it looks like it does a lot of things Right. Interesting. A-A-P seems to have similar use cases. I should take a serious look at it (and at Gentoo.) I hope it's not too closely tied with Vim, though... ;-) Shane ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Hi, new to zope
Hi Andreas it worked that file was owned by root, although it has 777 permission.!!?? anyway, I worked after the zope user took control of the file and also after putting in z2.py those lines...thanks -Original Message- From: Andreas Jung [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 10:51 AM To: Ramon Linan Cc: [EMAIL PROTECTED] Subject: RE: [Zope-dev] Hi, new to zope And maybe check the filepermissions of your _mysql.so file! It must be readable by python! -aj --On Donnerstag, 19. Juni 2003 16:41 Uhr +0200 Andreas Jung [EMAIL PROTECTED] wrote: add the following to your z2.py: import sys print sys.path Check the output against your PYTHONPATH. -aj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
http://www.a-a-p.org/index.html This looks quite good! It has support python 2.2 support as well. I'll see if I can play with it. Pieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] ./configure on Zope27HEAD with Python 2.2.2
Hi, Just ran ./configure using Python 2.2.2. I got the following output: (on FreeBSD 5.0) Configuring Zope installation Testing for an acceptable Python interpreter... Python version 2.2.2 found at /usr/local/bin/python let: arith: syntax error: i = i + 1 let: arith: syntax error: i = i + 1 [: 1: unexpected operator let: arith: syntax error: i = i + 1 [: 1: unexpected operator let: arith: syntax error: i = i + 1 [: 1: unexpected operator let: arith: syntax error: i = i + 1 FreeBSD's shell doesn't support let i=i+1 constructs: It works fine if I change the shell to /usr/local/bin/bash. An ugly fix seems to be to rename configure to configure.bash and create a configure such as: #!/bin/sh # force bash shell `which bash` ./configure.bash Other fix is to explain in the docs that you need to run bash ./configure on systems such as FreeBSD Anybody knows a nicer way to fix this? Pieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ./configure on Zope27HEAD with Python 2.2.2
Thanks for the warning. I know very little about BSD's shell (I don't even know what the default BSD shell is). FWIW, the need for bash is mentioned in INSTALL.txt (although I admit I thought it would work under other shells). Does anyone care enough to fix configure to work properly on BSD? On Thu, 2003-06-19 at 19:39, PieterB wrote: Hi, Just ran ./configure using Python 2.2.2. I got the following output: (on FreeBSD 5.0) Configuring Zope installation Testing for an acceptable Python interpreter... Python version 2.2.2 found at /usr/local/bin/python let: arith: syntax error: i = i + 1 let: arith: syntax error: i = i + 1 [: 1: unexpected operator let: arith: syntax error: i = i + 1 [: 1: unexpected operator let: arith: syntax error: i = i + 1 [: 1: unexpected operator let: arith: syntax error: i = i + 1 FreeBSD's shell doesn't support let i=i+1 constructs: It works fine if I change the shell to /usr/local/bin/bash. An ugly fix seems to be to rename configure to configure.bash and create a configure such as: #!/bin/sh # force bash shell `which bash` ./configure.bash Other fix is to explain in the docs that you need to run bash ./configure on systems such as FreeBSD Anybody knows a nicer way to fix this? Pieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On June 19, Chris McDonough wrote: On Wed, 2003-06-18 at 23:13, Adrian van den Dries wrote: python2.1 configure.py --prefix=/opt/zope271-python21 (FWIW, configure is a shell script.) Yes, I knew that. I used the .py extension for all the scripts to be consistent, according to my earlier point to this end. It too is just a shell wrapper to find the correct python and palm off the remaining options to inst/configure.py. Why not avoid that altogether and let the user supply the correct python? Ie, instead of:: ./configure --with-python=/usr/bin/python3.2 --other --options you call:: /usr/bin/python3.2 configure.py --other --options Which it pretty much does, anyway. I also see things like this: # Up to six acceptable python versions are allowed. Why six? Where is it enforced? Are you implying that the stuff that currently goes into software_home/lib/python would be installed to the site-package directory of the Python that was used to invoke the installer? If so, the subsequent invocations above of: No, I'm saying that the systems should be allowed (or even encouraged) to do this. We already have sys.path and namespaces. In a 1:1 python:zope environment, this should be enough to identify the Zope packages. Hence installing into python's module path. For multiple-version environments, you need --home (see below). cd Zope-2.7.1 python2.1 configure.py --prefix=/opt/zope271-python21 make; make install cd ../Zope-2.7.2 python2.1 configure.py --prefix=/opt/zope272-python21 make; make install ... would cause the Zope 2.7.1 libraries to be stomped by the Zope 2.7.2 libraries. No, because --prefix just told configure.py to install *everything* in that location. If you want to alias this option to --home, that would probably make this clearer, but I don't think it's different in function. If you mean that the libraries are installed into /opt/zope27X-python21/lib/python, there's no problem and nothing about the installer needs to be changed. Aye. So, in any case, given that the ZC source tarball installer will not attempt to manage multiple instances (we'll leave that to Luca) Aye. here are the requirements I've gathered so far: - Add a --doc flag to configure - Add a --skel flag to configure (is this a common pattern?) I think so. But consider using the Make variables suggested earlier, so that distributions may customise the make step: ./configure --options --supplied --by --zope make SITE=local SPECIFIC=options - Make it possible to install Zope libraries into the site-packages directory of the Python that invokes Zope's setup.py instead of into software_home/lib/python. As long as each of the top-level Zope directories in the --home (bin, doc, lib, skel) can be individually tweaked, either in the configure.py or the makefile, I think we win both ways. Am I missing anything? Apart from my personal desire to see the shell scripts deprecated, nope. ;-) I think that's covered everything that concerns Zope itself, and the rest gets palmed off to zopectl and packagers. a. -- Adrian van den Dries [EMAIL PROTECTED] Development team www.dev.flow.com.au FLOW Communications Pty. Ltd. www.flow.com.au ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ./configure on Zope27HEAD with Python 2.2.2
Does anyone care enough to fix configure to work properly on BSD? i=$(($i+1)) -- Jamie Heilman http://audible.transient.net/~jamie/ You came all this way, without saying squat, and now you're trying to tell me a '56 Chevy can beat a '47 Buick in a dead quarter mile? I liked you better when you weren't saying squat kid. -Buddy ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Thu, 2003-06-19 at 20:24, Adrian van den Dries wrote: On June 19, Chris McDonough wrote: On Wed, 2003-06-18 at 23:13, Adrian van den Dries wrote: python2.1 configure.py --prefix=/opt/zope271-python21 (FWIW, configure is a shell script.) Yes, I knew that. I used the .py extension for all the scripts to be consistent, according to my earlier point to this end. It too is just a shell wrapper to find the correct python and palm off the remaining options to inst/configure.py. Why not avoid that altogether and let the user supply the correct python? This is somewhat of a style choice, but many people who come to Zope don't know much about Python. It is friendlier (imho) to inform them they need to install a particular Python version (and where to get it) to get Zope running after they invoke 'configure' without a Python around rather than force them to read docs ahead of time to understand this. But there is no need to use the shell wrapper. It's purely a convenience for this kind of user. Power users can use inst/configure.py directly if they so choose. But I'm not going to document it because if they're smart enough to know Python, they're probably smart enough to know they can invoke it this way by reading the shell script (as you were). Ie, instead of:: ./configure --with-python=/usr/bin/python3.2 --other --options you call:: /usr/bin/python3.2 configure.py --other --options Which it pretty much does, anyway. Right. I also see things like this: # Up to six acceptable python versions are allowed. Why six? Where is it enforced? Well, as we all know, shell scripting kinda blows. There is no way that I know of to portably use an array in shell, and I wanted to eventually make it possible to use something other than bash to run the configure script (bash has arrays, but I'm not sure if bourne shell does). So, in any case, to get around this limitation, we have $FOUND1 - $FOUND6 variables which keep the result of the search for acceptable Python versions. It's enforced by the use of these variables. Were we to want more, we'd just create a $FOUND7 and so on. It probably could be made better, but I'd encourage you to just not look at this if it bothers you and use the inst/configure.py script directly. The shell script isn't particularly pretty, good, or elegant, but it serves its purpose. Are you implying that the stuff that currently goes into software_home/lib/python would be installed to the site-package directory of the Python that was used to invoke the installer? If so, the subsequent invocations above of: No, I'm saying that the systems should be allowed (or even encouraged) to do this. I agree they should be allowed. We already have sys.path and namespaces. In a 1:1 python:zope environment, this should be enough to identify the Zope packages. Hence installing into python's module path. For multiple-version environments, you need --home (see below). cd Zope-2.7.1 python2.1 configure.py --prefix=/opt/zope271-python21 make; make install cd ../Zope-2.7.2 python2.1 configure.py --prefix=/opt/zope272-python21 make; make install ... would cause the Zope 2.7.1 libraries to be stomped by the Zope 2.7.2 libraries. No, because --prefix just told configure.py to install *everything* in that location. If you want to alias this option to --home, that would probably make this clearer, but I don't think it's different in function. I think I understand at least half of that. Let me see if I can restate it. You're suggesting that --prefix be changed to --home. You're suggesting that specifying a --home implies that libraries will be installed to $home/lib/python. This is where I get a little confused. How does a user signify that Zope libraries should get installed into the Python site-package directory? What happens if --home is left unspecified? Is the --prefix option still around? If so, what does it do? Can you give an example of a configure command that would imply that Zope libraries get installed to site-packages? here are the requirements I've gathered so far: - Add a --doc flag to configure - Add a --skel flag to configure (is this a common pattern?) I think so. But consider using the Make variables suggested earlier, so that distributions may customise the make step: ./configure --options --supplied --by --zope make SITE=local SPECIFIC=options I think it is possible to tweak many things now via make -e after examination of the makefile. - Make it possible to install Zope libraries into the site-packages directory of the Python that invokes Zope's setup.py instead of into software_home/lib/python. As long as each of the top-level Zope directories in the --home (bin, doc, lib, skel) can be individually tweaked, either in the configure.py or the makefile, I think we win both ways. Great. Am I missing anything? Apart from my
Re: [Zope-dev] ./configure on Zope27HEAD with Python 2.2.2
Cool, thanks! On Thu, 2003-06-19 at 20:52, Jamie Heilman wrote: Does anyone care enough to fix configure to work properly on BSD? i=$(($i+1)) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] A-A-P and Zope 2.7 issues
Hi, I created a first draft cut of a A-A-P file for Zope/Python and Zope products. I think of using it for creating a zopetest product and a new FreeBSD zopetest port (a Makefile that uses 'aap' and can be used to create several zopeinstances with several sets of products. I also would like to write some scripts which can be used to do functional/performance tests (on the various Zope/Python versions on various platforms). I think that would really be usefull for the Zope continuous integration process. The current script (invoke with 'aap') downloads Python 2.2.3 and PyXML, builds and tests Python, gets Zope from CVS and configures Zope. Have a look at: http://gewis.nl/~pieterb/zope/zopetest/main.aap-v0.01.txt and rename it to main.aap. Some Zopeissues I ran into: --- As a followup to: http://collector.zope.org/Zope/952 When you specify a python using --with-python you don't get warned about whether you use a non-optimal python or not. Maybe it's also good to mention the user that he/she IS using the optimal python version, when he/she does so. -- Please rename the makefile to Makefile --- zopectl has a hardcoded PYTHON variable set to: PYTHON=/usr/local/bin/python shouldn't it use the --with-python version? --- ZConfig requires PyXML. Default Python doesn't provide it. Both zopectl using Python 2.2.2 and Python 2.2.3 give the following traceback: ./zopectl start Traceback (most recent call last): File /tmp/zope/lib/python/Zope/Startup/zopectl.py, line 148, in ? main() File /tmp/zope/lib/python/Zope/Startup/zopectl.py, line 131, in main options.realize(args) File /tmp/zope/lib/python/Zope/Startup/zopectl.py, line 80, in realize ZDOptions.realize(self, *args, **kw) File /tmp/zope/lib/python/zdaemon/zdoptions.py, line 257, in realize self.load_schema() File /tmp/zope/lib/python/zdaemon/zdoptions.py, line 298, in load_schema self.schema = ZConfig.loadSchema(self.schemafile) File /tmp/zope/lib/python/ZConfig/loader.py, line 36, in loadSchema return SchemaLoader().loadURL(url) File /tmp/zope/lib/python/ZConfig/loader.py, line 70, in loadURL return self.loadResource(r) File /tmp/zope/lib/python/ZConfig/loader.py, line 134, in loadResource self.registry, self) File /tmp/zope/lib/python/ZConfig/schema.py, line 42, in parseResource xml.sax.parse(resource.file, parser) File /usr/local/lib/python2.2/xml/sax/__init__.py, line 30, in parse parser = make_parser() File /usr/local/lib/python2.2/xml/sax/__init__.py, line 93, in make_parser raise SAXReaderNotAvailable(No parsers found, None) xml.sax._exceptions.SAXReaderNotAvailable: No parsers found Shouldn't ./configure already check this? -- The doc/INSTALL.txt states: The Python you run Zope with *must* have threads compiled in, which is the case for a vanilla build. Warning: Zope will not run with a Python version that uses libpth. You *must* use libpthread. Can this be checked when running ./configure? ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ./configure on Zope27HEAD with Python 2.2.2
Jamie Heilman writes: Does anyone care enough to fix configure to work properly on BSD? i=$(($i+1)) Whatever happened to the old tried-but-true: i=`expr $i + 1` Running an external process may be slower, but you don't need to run ./configure all that often unless you're developing Zope itself (and even then, not all *that* often). I suspect using expr is more portable to the whole family of sh-derived shells than any of the more new-fangled ways. Sheesh, who ever imagined I'd be the curmudgeon? -Fred -- Fred L. Drake, Jr. fred at zope.com PythonLabs at Zope Corporation ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ./configure on Zope27HEAD with Python 2.2.2
Fred L. Drake, Jr. wrote: Whatever happened to the old tried-but-true: i=`expr $i + 1` nothing, its just overkill I suspect using expr is more portable to the whole family of sh-derived shells than any of the more new-fangled ways. Arithmetic expansion has been around for a long time, I wouldn't worry about it. -- Jamie Heilman http://audible.transient.net/~jamie/ I was in love once -- a Sinclair ZX-81. People said, No, Holly, she's not for you. She was cheap, she was stupid and she wouldn't load -- well, not for me, anyway. -Holly ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Friday 20 June 2003 01:19 am, Jean Jordaan wrote: There's only one possible way! A-A-P! (A good match for Ape, Shane ;) It's a replacement for make by Bram Moolenaar, the author of Vim, and it looks like it does a lot of things Right. Sorry, I haven't really been paying attention so this might be completely OT. It *sounds* like it's being suggested that we replace make (given the above statement). Has anyone used SCons? http://www.scons.org/ Richard pgp0.pgp Description: signature
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On June 19, Chris McDonough wrote:
On Thu, 2003-06-19 at 20:24, Adrian van den Dries wrote:
Why not avoid that altogether and let the user supply the
correct python?
This is somewhat of a style choice
OK, ZC's call. ;-)
Well, as we all know, shell scripting kinda blows. There is no way that
I know of to portably use an array in shell, and I wanted to eventually
make it possible to use something other than bash to run the configure
script (bash has arrays, but I'm not sure if bourne shell does).
You may be interested in Kenneth Almquist's ash (aka dash in Debian):
Description: The Debian Almquist Shell
dash is a POSIX compliant shell that is much smaller than bash.
We take advantage of that by making it the shell on the installation
root floppy, where space is at a premium.
.
It can be usefully installed as /bin/sh (because it executes scripts
somewhat faster than bash), or as the default shell either of root
or of a second user with a userid of 0 (because it depends on fewer
libraries, and is therefore less likely to be affected by an upgrade
problem or a disk failure). It is also useful for checking that a
script uses only POSIX syntax.
You're suggesting that --prefix be changed to --home.
...
You're suggesting that specifying a --home implies that libraries will
be installed to $home/lib/python.
This is where I get a little confused. How does a user signify that
Zope libraries should get installed into the Python site-package
directory? What happens if --home is left unspecified? Is the
--prefix option still around? If so, what does it do? Can you give
an example of a configure command that would imply that Zope libraries
get installed to site-packages?
Erm, yes. I originally wanted --home and --prefix aliased, but I've
changed my mind. It should mirror the behaviour of the same options
to the distutils' install target.
With the distutils, ``--home`` is version-agnostic (installs package
``foo`` into ``$HOME/lib/python/foo/``) and ``--prefix`` is
version-aware (installs into ``$PREFIX/lib/pythonX.Y/site-packages``).
``inst/Makefile.in`` could probably be updated to do a --prefix install
if $(PREFIX) is defined, else it defaults to a --home install.
(Mockups)
# the next commands are all equivalent
# and produce the install target
# ``python setup.py --home=/usr/local/zope``
python inst/configure.py --home=/usr/local/zope
./configure --home=/usr/local/zope
./configure
# the next command produces the install target
# ``python setup.py --prefix=/usr/local``
# which installs packages to /usr/local/lib/python2.2/site-packages
python inst/configure.py --prefix=/usr/local
I think it is possible to tweak many things now via make -e after
examination of the makefile.
OK, that is what the Deb should do.
Well, if you ignore the shell scripts, I think we're ok, then!
Peaches!
...
(Couple of hours later).
OK, attached is a patch to inst/Makefile.in and inst/configure.py that
distinguishes --home and --prefix parameters and passes them onto the
distutils. But for some reason, there is still no difference between
--prefix and --home, even though it's passing those options to the
distutils. I suspect it might have something to do with this exerpt
from setup.py::
# We create a custom install scheme that works the same way on all
# platforms. We do this in order to prevent distutils from trying to
# guess where to put our files on a per-platform basis.
ZOPE_INSTALL_SCHEME = {
'purelib': '$base/lib/python',
'platlib': '$base/lib/python',
'headers': '$base/lib/python',
'scripts': '$base/bin',
'data' : '$base/lib/python',
}
That looks a little evil to me.
a.
--
Adrian van den Dries [EMAIL PROTECTED]
Development team www.dev.flow.com.au
FLOW Communications Pty. Ltd. www.flow.com.au
Index: doc/INSTALL.txt
===
RCS file: /var/lib/cvs/flowcom/Zope/dist/doc/INSTALL.txt,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 INSTALL.txt
--- doc/INSTALL.txt 18 Jun 2003 02:27:46 - 1.1.1.1
+++ doc/INSTALL.txt 20 Jun 2003 05:03:29 -
@@ -13,7 +13,7 @@
Recommendations
- - You are recommended to build and install Zope as a non-root user.
+ - We recommend you build and install Zope as a non-root user.
Building Zope
@@ -23,8 +23,25 @@
./configure --prefix=/where/to/install/zope
make
- If you do not specify a '--prefix' option, during a later step, Zope
- will be installed into a default location.
+ or
+
+./configure --home=/where/to/install/zope
+make
+
+ If you do not specify the '--home' or '--prefix' options, during a
+ later step, Zope will be installed into a default location.
+
+ --prefix differs from --home by installing Python packages into
+ $PREFIX/lib/pythonX.Y/site-packages, where --home installs the
+ packages
