Hi,
At Mon, 20 May 2013 19:33:43 -0700,
Russ Allbery wrote:
>
> Guillem Jover writes:
>
> > Perhaps, but I think we just lack better documentation and advice when
> > it comes to shared library handling in general.
>
> > There was an attempt by Junichi Uekawa (CCed) some time ago [L], but
> >
Le Mon, May 20, 2013 at 07:33:43PM -0700, Russ Allbery a écrit :
> Guillem Jover writes:
>
> > Perhaps, but I think we just lack better documentation and advice when
> > it comes to shared library handling in general.
>
> > There was an attempt by Junichi Uekawa (CCed) some time ago [L], but
> >
Guillem Jover writes:
> Perhaps, but I think we just lack better documentation and advice when
> it comes to shared library handling in general.
> There was an attempt by Junichi Uekawa (CCed) some time ago [L], but
> AFAIR some people shunned it because supposedly it contained inaccuracies
> or
Hi!
[ Just saw while drafting this, that you filed the bug on policy, so
sending a copy there too, let's continue the discussion there then. ]
On Wed, 2013-05-15 at 09:51:23 -0700, Russ Allbery wrote:
> Andreas Beckmann writes:
> > On 2013-05-15 09:58, Ondřej Surý wrote:
> >> The '2' in libgd2
Russ Allbery (16/05/2013):
> Package: debian-policy
> Severity: normal
>
> Policy 8.4 currently says:
>
> If there are development files associated with a shared library,
> the source package needs to generate a binary development package
> named librarynamesoversion-dev, or if you p
Package: debian-policy
Severity: normal
Policy 8.4 currently says:
If there are development files associated with a shared library,
the source package needs to generate a binary development package
named librarynamesoversion-dev, or if you prefer only to support one
development ve
6 matches
Mail list logo
