On Mon, Jan 13, 2003 at 09:55:48PM -0800, j_post wrote:
> On Monday 13 January 2003 09:00 pm, you wrote:
> >
> > A major revision of a libray might involve revisions to the API
> > (such as changes to function parameters, or contents of
> > data structures) and
> > so anything built with libabc-1 might crash with libabc-2.
> > You often need to install both.
> >
> Understood. But rpm will not install both--at least I haven't figured how to
> get it to do both.
It's not an rpm issue - it's an issue for those who wrote the
dependencies within the package. When I was running a Mandrake release
a couple of years back, I installed multiple versions of libraries -
their rpms allowed this.
Note, however, that many packages have strict requirements - they won't
work with older or newer versions of the library.
This is not really a Red Hat Linux issue - it's an issue with all OS's
that use shared files. Inevitably one app will require a different
version of a shared file than another app. That's one of the
disadvantages of using shared libraries. If you don't like it, compile
all your applications with static libraries - your file sizes will
baloon, but you won't have dependency issues.
.../Ed
--
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]
Member #1, Red Hat Community Ambassador Program
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
