Linux/Redhat advice : RPMs vs Src for Zope development ?
I find myself finally having to embrace that OS which is fast becoming the Microsoft of the linux world - Redhat. Coming from a FreeBSD background, I trust it won't be too much of a culture shock but have one question in particular : On FreeBSD, we have 'packages' and 'ports' which make installation of software quite easy. I notice that linux has its RPM's which are even more extensive - going down to the Zope product level in some cases. However, despite having these handy packages on FreeBSD, I've personally found it better to compile everything from src and ignore the packages/ports ... for example, I often need to recompile Python to include the MySQLmodule... but generally, sooner or later I need something adding or patching that was not in the package/port. So, my question is : If you were installing Python 1.5.2, Zope 2.1.1 and all the products/adapters to work with Postgres, MySQL, Oracle on Redhat 6.0, would you use the RPMs or go with src ? I know it may sound like a pedantic question - and that it perhaps shouldn't matter which you use - but from recent posts, it appears that sometimes RPMs work much better than src and sometimes they don't. And I'm just hoping I can avoid a few frustrating hours, Apologies if this question should be filed under "clueless". chas
hi chas, from my own experience using RH 5.2, 6.0 and 6.1 i came up with a combination of - MySQL RPMs - Python 1.5.2 RPMs (these are now part of RH 6.1 out of the box btw) - Zope src.tgz oracle comes in its own installer format AFAIK so the question doesn't really apply. it is tricky whichever way you choose ;) i haven't used PostGreSQL yet so i can't say anything about it. one warning: it seems that the very latest MySQL doesn't play nice with the MySQL adapters, i have 3.22.23b and it works flawlessly using just ZMySQLDA without the additional MySQL adapter packages that seem to have cropped up lately. jens
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of chas Sent: Tuesday, December 21, 1999 15:23 To: zope@zope.org Subject: [Zope] Linux/Redhat advice : RPMs vs Src for Zope development ?
I find myself finally having to embrace that OS which is fast becoming the Microsoft of the linux world - Redhat. Coming from a FreeBSD background, I trust it won't be too much of a culture shock but have one question in particular :
On FreeBSD, we have 'packages' and 'ports' which make installation of software quite easy. I notice that linux has its RPM's which are even more extensive - going down to the Zope product level in some cases.
However, despite having these handy packages on FreeBSD, I've personally found it better to compile everything from src and ignore the packages/ports ... for example, I often need to recompile Python to include the MySQLmodule... but generally, sooner or later I need something adding or patching that was not in the package/port.
So, my question is : If you were installing Python 1.5.2, Zope 2.1.1 and all the products/adapters to work with Postgres, MySQL, Oracle on Redhat 6.0, would you use the RPMs or go with src ? I know it may sound like a pedantic question - and that it perhaps shouldn't matter which you use - but from recent posts, it appears that sometimes RPMs work much better than src and sometimes they don't. And I'm just hoping I can avoid a few frustrating hours,
Apologies if this question should be filed under "clueless".
chas
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Jens Vagelpohl wrote:
hi chas,
from my own experience using RH 5.2, 6.0 and 6.1 i came up with a combination of
- MySQL RPMs - Python 1.5.2 RPMs (these are now part of RH 6.1 out of the box btw) - Zope src.tgz
oracle comes in its own installer format AFAIK so the question doesn't really apply. it is tricky whichever way you choose ;)
i haven't used PostGreSQL yet so i can't say anything about it.
one warning: it seems that the very latest MySQL doesn't play nice with the MySQL adapters, i have 3.22.23b and it works flawlessly using just ZMySQLDA without the additional MySQL adapter packages that seem to have cropped up lately.
I agree with everything above, except that I build python from source so that I can include all of the features that I want. As for adding things like the MySQL code to python, I don't know about BSD, but linux lets you add them as a dynamically loadable module, so there is no need to recompile the entire python interpreter. I generally prefer the control of compiling everything myself. The one exception is with MySQL, since they recommend using the rpms, which are compiled with every possible optimization. Watch out, though as anything newer than 3.22.25 doesn not work with the ZMySQLDA. I know that you can find a .25 version of the rpms at linuxmandrake.com
I'd just like to say a big thank you to everyone for the advice on the RPMs vs Src when setting up a Zope application development environment (incl databases etc) on Linux (RH in particular). Some of the tips/advice have definitely saved me potentially days of frustration (eg. ZMySQLDA only working with older versions of MySQL) as well as given me a much better idea of what I'm letting myself in for. Now for some hands-on :) Thank you again, chas
+----[ chas ]--------------------------------------------- | I find myself finally having to embrace that OS which is | fast becoming the Microsoft of the linux world - Redhat. No that's SCO Unix (almost literally :-) | However, despite having these handy packages on FreeBSD, | I've personally found it better to compile everything | from src and ignore the packages/ports ... | for example, I often need to recompile Python to include | the MySQLmodule... but generally, sooner or later I need | something adding or patching that was not in the package/port. I used to be the same way. Install the package or the port. You will find that if someone has a port for an addon it will integrate nicely. You will also find that the port installs most of the common options required. FWIW I'm running python + mysql out of ports + Zope (not out of ports). I have had no problems at all. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|
So, my question is : If you were installing Python 1.5.2, Zope 2.1.1 and all the products/adapters to work with Postgres, MySQL, Oracle on Redhat 6.0, would you use the RPMs or go with src ? I know it may sound like a pedantic question - and that it perhaps shouldn't matter which you use - but from recent posts, it appears that sometimes RPMs work much better than src and sometimes they don't. And I'm just hoping I can avoid a few frustrating hours,
my view: rpms provide better management. you can install and uninstall with ease. and i think most rpms come with all/most parameters compiled in. but src gives you the speed me think(correct me if i'm wrong) since it's optimized for *your* machine.. but in real life, i went with postgres rpm, python rpm, and zope src. i current;y have no hands on oracle or mysql yet. so, i think a mix of both is in order. ------------------------------------------------------ http://www.kedai.com.my/kk Am I Evil?
- wrote:
So, my question is : If you were installing Python 1.5.2, Zope 2.1.1 and all the products/adapters to work with Postgres, MySQL, Oracle on Redhat 6.0, would you use the RPMs or go with src ? I know it may sound like a pedantic question - and that it perhaps shouldn't matter which you use - but from recent posts, it appears that sometimes RPMs work much better than src and sometimes they don't. And I'm just hoping I can avoid a few frustrating hours,
my view: rpms provide better management. you can install and uninstall with ease. and i think most rpms come with all/most parameters compiled in.
but src gives you the speed me think(correct me if i'm wrong) since it's optimized for *your* machine.. but in real life, i went with postgres rpm, python rpm, and zope src. i current;y have no hands on oracle or mysql yet.
so, i think a mix of both is in order.
Luckily, it exists :^) Download the source rpm (.src.rpm), adjust if needed, and rebuild. The install the rpm you just built. -- In flying I have learned that carelessness and overconfidence are usually far more dangerous than deliberately accepted risks. -- Wilbur Wright in a letter to his father, September 1900
my view: rpms provide better management. you can install and uninstall with ease. and i think most rpms come with all/most parameters compiled in.
My preference is almost always source. I don't however like the mess of just installing whatever all into /usr/local. What i've been using is stow (ftp://ftp.gnu.org/gnu/stow), which allows me to install each package i compile into a structure like /usr/local/stow/packagename, and then it sym links it into the /usr/local tree, meaning that everything works the same, but i can now uninstall or temp uninstall on the fly, i can find which package a file came from or which files a package came with, and i can move stuff off to other file systems if i get tight on space. Very sweet! sRp
On Fri, 24 Dec 1999, you wrote:
my view: rpms provide better management. you can install and uninstall with ease. and i think most rpms come with all/most parameters compiled in.
My preference is almost always source. I don't however like the mess of just installing whatever all into /usr/local. What i've been using is stow (ftp://ftp.gnu.org/gnu/stow), which allows me to install each package i compile into a structure like /usr/local/stow/packagename, and then it sym links it into the /usr/local tree, meaning that everything works the same, but i can now uninstall or temp uninstall on the fly, i can find which package a file came from or which files a package came with, and i can move stuff off to other file systems if i get tight on space. Very sweet!
true. as someone has mentioned eralier, there's also src rpm; which totally slipped my mind (maybe not enought food that day). so, you get both management and binary for *your* machine. all in all, either rpms or tar ball - both depends on our preference. ------------------------------------------------------ http://www.kedai.com.my/kk Am I Evil?
chas wrote:
I find myself finally having to embrace that OS which is fast becoming the Microsoft of the linux world - Redhat.
<grin>
Coming from a FreeBSD background, I trust it won't be too much of a culture shock but have one question in particular :
On FreeBSD, we have 'packages' and 'ports' which make installation of software quite easy. I notice that linux has its RPM's which are even more extensive - going down to the Zope product level in some cases.
i also came to RedHat-based linux (BlackCat) having FreeBD background, and i miss the ports collection very much.
would you use the RPMs or go with src ?
in most cases, i prefer to fetch (or make myself) the source rpm, and build binary rpms on my computer. this gives me the better chance that the package is built with right libraries (which is not always the case for binaries packed elsewhere), and allows to remove/upgrade the package more easily and to share the binaries with my colleagues. best wishes, alex.
participants (8)
-
- -
alexander smishlajev -
Andrew Kenneth Milton -
Bill Anderson -
chas -
Jens Vagelpohl -
Sam Gendler -
Scott Parish