On Thu, Oct 14, 2004 at 08:32:47PM +0200, Daniel Stenberg wrote:
> On Wed, 13 Oct 2004, Dan Fandrich wrote:
> >However, you can't install two different
> >libcurl packages without RPM complaining about a duplicate file in that
> >case.
>
> Aren't there any other packages that have the same problem? If so, how do
> theý generally solve it?

Programs like gimp and gphoto use the second technique I proposed and store
their required files in a directory named after the version number of the
package. That lets you install several versions of libraries without a
conflict, as long as the SONAMEs are different, of course, but the SONAME
is supposed to change when the library is no longer backwards-compatible.

> What about devel packages that have include files etc? What if you install
> two of those?

I haven't seen a packaging system that handles that cleanly, nor have
I found a need to do it personally. I wouldn't be difficult to do--all
the devel files could go into a new directory based on the version number
and pkg-config could handle setting the right include path.

> ... and that seems wrong, since the ca certs might be useful to any app
> that uses libcurl.

Indeed.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved