Re: Dependencies on shared libs, take 2
On Wed, Jun 06, 2007, Raphael Hertzog wrote:
> We could then have the package field contain multiple packages (separated
> by "," or "|" or whatever) and have dpkg-shlibdeps generate pkg1 (>=
> min-ver) | pkg2 (>= min-ver).
I don't think so; at least sometimes you want to depend on
non-versionned packages, such as virtual provides for ABIs and such.
For example libnotify1.shlibs:
libnotify 1 libnotify1 (>= 0.4.4), libnotify1-gtk2.10
--
Loïc Minier
Reply to:
- References:
- Re: Dependencies on shared libs, take 2
- From: Josselin Mouette <joss@debian.org>
- Re: Dependencies on shared libs, take 2
- From: Raphael Hertzog <hertzog@debian.org>
- Re: Dependencies on shared libs, take 2
- From: Josselin Mouette <joss@debian.org>
- Re: Dependencies on shared libs, take 2
- From: Steve Langasek <vorlon@debian.org>
- Re: Dependencies on shared libs, take 2
- From: Mike Hommey <mh@glandium.org>
- Re: Dependencies on shared libs, take 2
- From: Steve Langasek <vorlon@debian.org>
- Re: Dependencies on shared libs, take 2
- From: Joey Hess <joeyh@debian.org>
- Re: Dependencies on shared libs, take 2
- From: Mike Hommey <mh@glandium.org>
- Re: Dependencies on shared libs, take 2
- From: Steve Langasek <vorlon@debian.org>
- Re: Dependencies on shared libs, take 2
- From: Raphael Hertzog <hertzog@debian.org>