On Tue, Jun 10, 2003, Michael van Elst wrote:
> > I'm not sure whether I understand your correctly. Are you talking about
> > a not triggered rebuild in openpkg-tool or about the fact that the
> > package does break on a plain rebuilding?
> >
> > I guess you're talking about the first. And here I do not understand:
> > in all of our applications, we never have a run-time dependency to
> > libraries which were needed under build-time.
>
> I beg to differ, we have many such dependencies. Dependencies to libraries
> are very often copied in BuildPreReq and PreReq.
Then those packages are incorrect IMHO.
> The PreReq dependency is required to trigger rebuilds because this
> is the only kind stored by rpm in the package database. The BuildPreReq
> information is lost.
But one can argue that it is just fair that RPM throws this info away
now (after installing) it is no longer required for it.
> Index information cannot be used as a substitute because it is only
> valid for packages in the repository which often do have dependencies
> different from installed packages.
Can you provide more details or an example? I'm not sure whether
I understand this correctly.
> N.B. whenever we start supporting shared libraries then the runtime
> dependency is even required for correct functioning of the dependent
> packages.
Yes, of course. But if we move to _shared_ libraries, then the library
packages are really technically run-time dependencies ;-)
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
