Bug#568374: debian-policy: section "8.4 Development files" not explicit enough regarding libraryname[soversion]-dev

2017-02-20 Thread Russ Allbery
Control: tag -1 pending Ansgar Burchardt writes: > I suggest to change > | 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

Bug#568374: debian-policy: section "8.4 Development files" not explicit enough regarding libraryname[soversion]-dev

2016-02-02 Thread Ansgar Burchardt
Hi, is there still something missing for this to be included in the next Policy update? Ansgar

Bug#568374: debian-policy: section "8.4 Development files" not explicit enough regarding libraryname[soversion]-dev

2015-11-02 Thread Cyril Brulebois
Ansgar Burchardt (2015-10-27): > Hi, > > I suggest to change > > | 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

Bug#568374: debian-policy: section "8.4 Development files" not explicit enough regarding libraryname[soversion]-dev

2015-10-27 Thread Ansgar Burchardt
Hi, I suggest to change | 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 version at a time, | libraryname-dev. to | If

Bug#568374: debian-policy: section "8.4 Development files" not explicit enough regarding libraryname[soversion]-dev

2015-10-27 Thread Tim Janik
On Tue, 27 Oct 2015 10:06:50 +0100 Ansgar Burchardt wrote: > | If there are development files associated with a shared > | library, the source package needs to generate a binary > | development package named libraryname-dev, or if you > | need to support multiple development

Bug#568374: debian-policy: section "8.4 Development files" not explicit enough regarding libraryname[soversion]-dev

2015-10-27 Thread Julien Cristau
On Tue, Oct 27, 2015 at 10:06:50 +0100, Ansgar Burchardt wrote: > Hi, > > I suggest to change > > | 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

Bug#568374: debian-policy: section "8.4 Development files" not explicit enough regarding libraryname[soversion]-dev

2015-10-27 Thread Emilio Pozuelo Monfort
On Tue, 27 Oct 2015 10:06:50 +0100 Ansgar Burchardt wrote: > Hi, > > I suggest to change > > | 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

Bug#568374: debian-policy: section "8.4 Development files" not explicit enough regarding libraryname[soversion]-dev

2015-10-27 Thread Jonathan Nieder
Emilio Pozuelo Monfort wrote: > On Tue, 27 Oct 2015 10:06:50 +0100 Ansgar Burchardt wrote: >> I suggest to change >> >> | If there are development files associated with a shared >> | library, the source package needs to generate a binary >> | development package named

Bug#568374: debian-policy: section 8.4 Development files not explicit enough regarding libraryname[soversion]-dev

2010-02-04 Thread Michael Prokop
Package: debian-policy Severity: wishlist Section 8.4 of the policy says: | 8.4 Development files | | The development files associated to a shared library need to be | placed in a package called librarynamesoversion-dev, or if you | prefer only to support one development version at a time, |