Re: *.so symlinks in shared lib package

2012-07-27 Thread Michael Wild
On 07/27/2012 10:34 AM, Russ Allbery wrote: > Michael Wild writes: > >> Do *.so development symlinks in a shared-library package constitute a >> policy violation? 8.1 Doesn't forbid them in the library package and 8.4 >> only says the "should" be in the -dev package. > > If the *.so development

Re: *.so symlinks in shared lib package

2012-07-27 Thread Russ Allbery
Michael Wild writes: > Do *.so development symlinks in a shared-library package constitute a > policy violation? 8.1 Doesn't forbid them in the library package and 8.4 > only says the "should" be in the -dev package. If the *.so development symlinks prevent two versions of the package with diffe

Re: *.so symlinks in shared lib package

2012-07-27 Thread Ansgar Burchardt
Michael Wild writes: > Do *.so development symlinks in a shared-library package constitute a > policy violation? 8.1 Doesn't forbid them in the library package and 8.4 > only says the "should" be in the -dev package. >From Policy 8.2: If your package contains files whose names do not change

*.so symlinks in shared lib package

2012-07-27 Thread Michael Wild
Hi all Do *.so development symlinks in a shared-library package constitute a policy violation? 8.1 Doesn't forbid them in the library package and 8.4 only says the "should" be in the -dev package. Thanks for the help in advance Michael -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.