[Zope] [Fwd: Questions on your ZmySQLDA Tutorial]

[Chris McDonough]

i iamge you've got the python libs installed in /usr/lib/python1.5

do the rpm -e python --force

go see if that directory is still there.  if so, delete it.

do 'find / -name "python*" -print', see if there are any straggles of
the source python you installed.  if so, delete them.  this would
happen, for instance, if you didn't specify the --prefix as "/usr" while
running "./configure" in the python source build.  you'll end up with a
dir /usr/local/python1.5 and a binary in /usr/local/bin/python and some
other junk in /usr/local/include and /usr/local/man.  this is a pain,
and python (to my knowledge) doesn't allow you to "make uninstall", so
it's unfortunately necessary.  this is why its advisable to install from
rpms if you're unfamiliar with python for the first time.

after you've tracked down all the stuff that got installed and delete
it, install the python 1.5.2 rpm, and the python-devel rpm.  or build
from source again, this time specifiying --prefix=/usr/bin
--with-threads"

Don Undeen wrote:
> 
> Oh dear,
>     Let me phrase this question properly for those that came in late...
> I have the Redhat6.1 installed python and Python from source both installed on my
> system.
> I've copied over some of the Redhat python with the source python.
> I want to eliminate any redundancy that may confuse my system, leaving only the
> source Python.
> if I do a "rpm -e python --force," will I then have to re-install python from
> Source?
> If I do have to re-install from source, will I have to remove the previous
> from-source Python?
> If so, what's the best way to do that?
> Is this method likely to screw up anything else?
> Thanks to everyone.
> Don Undeen
> dundee@gator.net
> 
> Chris McDonough wrote:
> 
> > "it's rpm -e python --force", I think.
> >
> > Don Undeen wrote:
> > >
> > > I see what you are saying, but what problems might this create, other than
> > > having extra libraries lytin around? Becuase I tried to rpm -e python
> > > --nodeps, but for some reason that didn't work out, so I went with this
> > > option instead.
> > > I wanted to re-re-install python, with your suggestion, would it still be as
> > > simple as what you've suggested. Given that I've already copied over the old
> > > python executable?
> > >
> > > elijah wright wrote:
> > >
> > > > >1. Fresh install of Redhat 6.1
> > > > >2. Installed Python from source, and copied over the  python that Redhat
> > > > >automatically installed.
> > > >
> > > > i've seen this same recommendation twice in the last couple of days... to
> > > > "just copy over the python executable redhat installed"....
> > > >
> > > > eventually, this is going to jump up and bite someone in the ass.  leaving
> > > > extra libraries lying around all over a system (which you're going to do
> > > > by 'just copy over' methods...) is quite a pain to clean up.
> > > >
> > > > the better solution would be:
> > > >
> > > > rpm -e python --nodeps
> > > > build python with threads enabled
> > > > do a make install
> > > > make sure your path knows about /usr/local/bin.
> > > >
> > > > elijah wright
> > > > elw@stderr.org
> > >
> > > _______________________________________________
> > > 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 )
> >
> > --
> > Chris McDonough - Digital Creations, Inc.
> > Publishers of Zope - http://www.zope.org

-- 
Chris McDonough - Digital Creations, Inc.
Publishers of Zope - http://www.zope.org