> I am not quite sure what you mean by "organizing the source tree",
> since
> you are supposed to have the unpacked sources from the upstream
> tarball,
> plus an additional debian/ folder containing the Debian specific
> files
> (control, copyright, rules...). This is common to all packaging
On 02/12/16 19:14, Diane Trout wrote:
I don't think this is a problem. Policy 4.13 [1] says
~~~
Debian packages should not make use of these convenience copies
unless
the included package is explicitly intended to be used in this way.
~~~
which I think matches the situation here.
Thank you
> I don't think this is a problem. Policy 4.13 [1] says
>
> ~~~
> Debian packages should not make use of these convenience copies
> unless
> the included package is explicitly intended to be used in this way.
> ~~~
>
> which I think matches the situation here.
Thank you for point that clause
Hello,
على الخميس 1 كانون الأول 2016 16:32، كتب Diane Trout:
> And instead of building a shared library, they just add the C files to
> the python C extension. See:
> https://github.com/dpryan79/pyBigWig/blob/master/setup.py#L14
>
> I believe this is a violation of Debian packaging policy, but
4 matches
Mail list logo