On Mon, 16 Feb 2004, Craig Daters wrote:

> I installed 0.65 on a RH9 system using the source install (as opposed
> to the RPM) and I now want to upgrade to 0.67 using the same method.
> What is the proper way to do this? Is there and uninstall/upgrade
> method for doing this?
>
> Or, do I just download it, un-tar the 0.67 files then run:
>
> $ ./configure --sysconfdir=/etc
> $ make
> $ su -c "make install"
>
> I seem to recall that someone had asked this, but cannot find it in the list.
>
> If I do have to un-install the 0.65 install, how do I go about this?
> I am used to working with RPM binaries, but I want to get into
> installing from source files instead to get a better idea of the
> installation process.
>
> Any help would be appreciated
>

Here's what I do personally which seems to work great;

I'm using Slackware Linux, and I build ClamAV from source. But, I don't
want to just do "make install" as that leaves me with the responsabillity
to manually clean out old versions by hand etc. So what I do instead is
use "checkinstall".  checkinstall is a tool that'll monitor an
installation done by "make install" and then it'll build a package for
your distribution that you can later uninstall or upgrade with your
distributions standard tools.  checkinstall can build both Slackware
packages, RPMs, Debian .deb packages etc.

Here's an example of how I do it (you would ofcourse use rpm in place of
my use of slackwares installpkg/removepkg/upgradepkg tools).

  ; First I configure clamav-0.65
$ ./configure <with whatever options I want to use>
  ; then I build it
$ make
  ; then we change to the root user to install/build package
$ su
  ; then we run checkinstall (which then runs 'make install' and monitor it)
# checkinstall -S
  ; the -S option tells checkinstall to build a Slackware package,
  ; you'd ofcourse want to build a RedHat one
  ; you can run checkinstall without any options and it will ask
  ; what distribution to build a package for
  ; now, after checkinstall finishes I'm left with a Slackware package
  ; named  clamav-0.65-i486-01.tgz which I can then install
# installpkg clamav-0.65-i486-01.tgz

  ; Now that was pretty easy...
  ; if I want to remove clam again I can now simply run
# removepkg clamav-0.65-i486-01
  ; just as with any other package

Now, let's assume I have 0.65 installed as pr the instructions above and I
download 0.67 and want to upgrade. Then I'd first build 0.67 *just like* I
did with the 0.65 version above. This time I'l be left with a package
called clamav-0.67-i486-01.tgz , and to upgrade I only have to run

# upgradepkg clamav-0.67-i486-01.tgz

And the magic happens :-)

Same thing with RedHat, except you'd use "rpm -i" etc to
install/remove/upgrade the generated packages.

You can find checkinstall here :
http://asic-linux.com.mx/~izto/checkinstall/index.php

I'm personally using the latest checkinstall-1.6.0beta3 version which
works like a charm.

You should read the very informative README file here :
http://asic-linux.com.mx/~izto/checkinstall/docs/README
If you want all the details, but simple usage like above should do you
just fine in most cases.

In my oppinion checkinstall is a life saver when doing a lot of source
installs of software.


Kind regards,

Jesper Juhl



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users

Reply via email to