I downloaded a program that needs the newer verson of zlib than SuSE allows.

The SuSE rpm combined the -devel with the regular rpm ($world calls it
zlib, SuSE calls it libz). If I do 'rpm -Uvh --test zlib.$VERSION.rpm
zlib-devel.$VERSION.rpm' I get conflicts from the -devel package.

If I use the replacefiles option I get no errors from rpm but I know
all software lies <g>. Is this likely to bite me in the arse?

--
I have an understanding with my local police--I have them outgunned, but
they have me outnumbered.

Report this post to a moderator

On Thu, 27 Jun 2002 23:34:25 -0500, Brad Sims wrote:

> I downloaded a program that needs the newer verson of zlib than SuSE allows.
>
> The SuSE rpm combined the -devel with the regular rpm ($world calls it
> zlib, SuSE calls it libz). If I do 'rpm -Uvh --test zlib.$VERSION.rpm
> zlib-devel.$VERSION.rpm' I get conflicts from the -devel package.
>
> If I use the replacefiles option I get no errors from rpm but I know
> all software lies <g>. Is this likely to bite me in the arse?

No idea on SuSE. I've been using it with Redhat for a long time with no
problems.

Since the *-devel packages are usually only need for building things that
require the libs and includes for that package, you might be able to get
away with just deleting the zlib-devel package altogether in some
instances. But since this is xlib, probably not.

You could use --replacefiles and see what happens. Then if you find
problems you could always reinstall it, or even go backward.

If I were opting for one of the choices, I think I'd go with
--replacefiles because I haven't had any problems at all caused by it.

Report this post to a moderator