Re: [Evolution] strange changes

[Paul Harouff <pharouff comcast net>]

On Tue, 2003-09-16 at 13:35, Kathy ODriscoll wrote:
> And I have tried the configure make make install thing, doesnt work for
> me the way it does for the rest of the linux community...yet anyway

I found that recent distributions don't work well unless you install new
applications with RPM files. The ./configure, make, make install
procedure doesn't update the dependency databases which screws up all
the other applications.

Sometimes, really good/generous programmers will include a *.spec file
in the package. If you see a file named programname.spec you can create
your own RPM. With SuSE you have to make some modifications. But, in
your case they are usually written for RH so you don't have to worry.

Procedure for using *.spec file (I'm not used to RH, so someone can
proofread this for me and make corrections if necessary):

> mkdir /usr/local/packages/programname

download programname-0.0.0.tar.gz to /usr/local/packages/programname
I use /usr/local/packages to help me keep track of what modifications I
have made to the system from 3rd party source files.

> cd /usr/local/packages/programname
> tar xzvf programname-0.0.0.tar.gz

This usually creates a directory programname-0.0.0/

> cd programname-0.0.0/

read the files README and INSTALL for special instructions

> cp programname.spec ../
> cd ..

following line is optional, you don't need the directory anymore

> rm -R programname-0.0.0/
> cp programname-0.0.0.tar.gz /usr/src/redhat/SOURCES
> rpm -ba programname.spec

if all goes well you will see two or three lines similar to
writing /usr/src/redhat/SRPMS/programname.rpm
writing /usr/src/redhat/RPMS/i386/programname.rpm
somewhere close to the end of all the messages. 

Some applications create multiple RPMs. If you see more than one
programname.rpm message you need to do the follow for each one of them:

> cp /usr/src/redhat/RPMS/i386/programname.rpm ./
> rpm -Uvh programname.rpm


==========
WHAT IF THERE IS NO *.spec FILE?

I gave up RH about a year ago, so I don't know how well this will work
for you. So far I've had good luck with SuSE.

Get checkinstall and use the following procedure to create a "fake" RPM
so the application is registered and you can use rpm -e to remove the
package when you don't want it anymore:
> ./configure
> make
> /usr/local/sbin/checkinstall

Before you run checkinstall, make sure that you have a one or two
sentence Summary: description of the program -- usually you can find
something useful in the README or on the website. You will be asked to
type this after you select create RPM. You may also want to have a list
of the "Provides:" files. It defaults to just Provides: programname, but
you can change it. Also, don't forget to check the version numbers.

If you need to get checkinstall, go to:

http://asic-linux.com.mx/~izto/checkinstall/index.php

Paul
Alexandria, VA