Roman Hodek wrote:
>
> > How do we ensure that someone upgrading a package from potato to woody
> > pulls in all of the required libraries? As a "concrete" example,
> > /usr/bin/foo in the foo package depends upon libbar directly and
> > libbar depends upon libbaz indirectly. In potato, libbar d
> "Julian" == Julian Gilbey <[EMAIL PROTECTED]> writes:
Julian> How do we ensure that someone upgrading a package from
Julian> potato to woody pulls in all of the required libraries?
Julian> As a "concrete" example, /usr/bin/foo in the foo package
Julian> depends upon libbar di
> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
Brian> I thought the solution was obvious - change the shared
Brian> library dependancy information on libbar
I meant to cancel this post, not send it! ARGGHHH!!!
Anyway, now I have sent it, I might as well complete what I was saying.
On Thu, 20 Jan 2000, Roman Hodek wrote:
> However (as already said in a previous mail) I think that most shlib
> packages already do depend on other libs they need. What about
> checking for libs that have no such dependencies first?
It would be a nasty bug if this is not the case, consider doin
On Thu, Jan 20, 2000 at 02:35:33PM +0100, Wichert Akkerman wrote:
> Previously Julian Gilbey wrote:
> > [I think that some version of the original message should be posted at
> > some point to -devel-announce, probably once the new dpkg-shlibdeps is
> > installed in woody. We also might need some
> Right, and I'm willing to bet that happens. Not everyone uses
> debhelper..
Sure, not everyone, but many. And not to forget, (AFAIK) debstd does
the same. Indeed, I always thought that shlib packages should depend
on the libs they need already... :-)
> I guess it could be done as a lintian che
Previously Julian Gilbey wrote:
> [I think that some version of the original message should be posted at
> some point to -devel-announce, probably once the new dpkg-shlibdeps is
> installed in woody. We also might need some NMUs if this occurs
> during the potato freeze and many developers are wor
Previously Roman Hodek wrote:
> The problem you describe can exist. But only if libbar doesn't depend
> yet on libbaz in potato.
Right, and I'm willing to bet that happens. Not everyone uses
debhelper..
> However (as already said in a previous mail) I think that most shlib
> packages already do d
> How do we ensure that someone upgrading a package from potato to woody
> pulls in all of the required libraries? As a "concrete" example,
> /usr/bin/foo in the foo package depends upon libbar directly and
> libbar depends upon libbaz indirectly. In potato, libbar does not
> declare a dependenc
[I think that some version of the original message should be posted at
some point to -devel-announce, probably once the new dpkg-shlibdeps is
installed in woody. We also might need some NMUs if this occurs
during the potato freeze and many developers are working on frozen
rather than unstable mach
10 matches
Mail list logo
