Subject: Re: Shared object not found - but all dependencies are ok ?!
To: Jeremy C. Reed <email@example.com>
From: Pavel Cahyna <firstname.lastname@example.org>
Date: 01/13/2005 20:11:24
> On Thu, 13 Jan 2005, Pavel Cahyna wrote:
> > > Improving pkg_add to correctly verify the PROVIDES versus REQUIRES before
> > > installation is any idea. I am not sure what it can say though -- "This
> > > package needs ..... I don't know what the package is called. Sorry."
> > Now I am thinking about this more, and I see that it is not sufficient,
> > because there will be often need to have multiple versions of a library
> > installed and I don't think that having multiple packages with the same
> > name is supported, so a version number in a package name will be still
> > needed. Or does pkgviews change something here?
> pkgviews won't help with your problem, because the problem is with having
> open-ended dependencies.
What exatcly are "open-ended dependencies"?
> > Also, a way to separate a package into multiple binary packages will be
> > needed, because while the different versions of a shared library have
> > non-conflicting filenames, the developement files (headers and ar archives)
> > and documentation don't. That's why in Debian library packages are split
> > to a runtime support package and a developement package. (It can also save
> > space and download dime for those who don't compile from source.)
> Not the same, but pkgviews will help here -- you can have the files with
> same filenames installed multiple times.
Hmmm, but they will all be in their respective depot direcories, no? How
to make selected files (those which don't have conflicting filenames, such
as shared libraries) from such packages appear in the "default view"?