[lug] best places to put builds?

Riggs, Robert RRiggs at doubleclick.net
Tue Mar 20 22:34:52 MST 2001

It sounds like you may have a couple of problems here. First off, it
sounds like you don't have all of the RH7 packages installed that you
need. ncurses4-5.0-2, readline2.2.1-2.2.1-2 are the RH7 packages that
you need for these libraries. Secondly, you probably have a Python2
RPM compiled for either an older RH version, or another RPM based
distribution, since the current development readline version for RH7
is readline-devel-4.1-5. (I could easily be wrong on this second point,
but it would be strange to link against older libraries, unless there
is a backwards compatibility issue.)

See if there is a Python2 package specifically for RH7.

But, to answer your question, generally /usr/local/src is the best
place for source packages (and allow them to install in the /usr/local
hierarchy). However, I would strongly recommend that you refrain from
installing from source tarballs whenever possible on RPM systems. It
makes system administration a nightmare after a while. And debugging
problems becomes really difficult when you don't know if you are
loading libraries from /usr/lib or /usr/local/lib.

You can almost always find the appropriate RPMs if you look hard enough.


-----Original Message-----
From: Keith C. Herold [mailto:herold at cslr.Colorado.EDU]
Sent: Tuesday, March 20, 2001 9:52 PM
To: lug at lug.boulder.co.us
Subject: [lug] best places to put builds?

Howdy!  I am a relative idiot in Linux (and the real world too, I suppose)
so I confuse easy (myself, I mean).

Occasionally I try to download new software for my linux boxes (all redhat
7.0 + 10 million updates), but there is either no rpm or for some reason the
rpm doesn't work.  When I download the source, I usually stick it in /root
and do the configure-make-crossfingers bit.  My question is, is there some
standard place to do this?

The latest problem is installing python 2.0.  The rpm's require
libncurses.so.4 and libreadline.so.3, but I can't find them, so I figured I
would use the sources.  After downloading,configureing and running make, I
am left with a python directory in the /root, and have been copying the
resulting executable to /usr/bin.  But, when I run the interpreter, it can't
find some of the modules (still runs, though).  Since it seems like a bad
idea to point things to the root directory, is there a good place to put
these sources for the build?


Web Page:  http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug

More information about the LUG mailing list