Re: [Zope-dev] Best practice for Zope-private copy of Python 2.1 onLinux?
On Mon, 6 May 2002, Jeff Kowalczyk wrote: > Python 2.2, I'll ask if there is, or suggest if there isn't, a shift due > in the installation procedures on Linux to optionally use a private copy > of Python 2.1, much like the Windows version of Zope does. That version Personally, I just do a 'make altinstall' on my python2.1, and then install Zope using the python2.1 command. That way, python2.1 is available for any other package on my system that might need the older python version. I don't really see any benefit, myself, to giving zope a private copy. --RDM ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Best practice for Zope-private copy of Python 2.1 onLinux?
On Mon, 2002-05-06 at 16:51, Andreas Jung wrote: > Compile python from source with --prefix=/your/privat/python/directory > and install it there. Then run the standard Zope installation > process with this new Python. That's it. I'd go one step further and suggest that you compile python with --prefix=/path/to/your/Zope, this way you end up with something that looks remarkably like the binary Zope distributed at Zope.org -- Ideas don't stay in some minds very long because they don't like solitary confinement. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
