Bug#1000637: generating debian/control is *NOT* policy compliant

2022-01-23 Thread Ondřej Surý
That’s exactly how it’s done in the PHP packages. If you see a different 
content in the debian/control, it means the packages were not generated in the 
clean build environment.

Ondřej
--
Ondřej Surý  (He/Him)

> On 23. 1. 2022, at 15:09, Thomas Goirand  wrote:
> 
> Hi,
> 
> Looks like the php-* PECL packages are getting their debian/control generated 
> at build time from a debian/control.in.
> 
> If you didn't know, this is *NOT* policy compliant. The policy clearly says 
> source packages must have a not-generated debian/control in good shape 
> (though I haven't taken the time to find where this is written in the policy, 
> I just know it's forbidden...). Please stop doing this.
> 
> If you still need to generate it, then you can have a look how the Linux 
> kernel package does it. They generate the debian/control from control.in 
> thanks to some internal tooling, but save the debian/control in the generated 
> form in their source package. That may be a nice workaround, and the better 
> way to go for you.
> 
> Cheers,
> 
> Thomas Goirand (zigo)
> 



Bug#1000637: generating debian/control is *NOT* policy compliant

2022-01-23 Thread Thomas Goirand

Hi,

Looks like the php-* PECL packages are getting their debian/control 
generated at build time from a debian/control.in.


If you didn't know, this is *NOT* policy compliant. The policy clearly 
says source packages must have a not-generated debian/control in good 
shape (though I haven't taken the time to find where this is written in 
the policy, I just know it's forbidden...). Please stop doing this.


If you still need to generate it, then you can have a look how the Linux 
kernel package does it. They generate the debian/control from control.in 
thanks to some internal tooling, but save the debian/control in the 
generated form in their source package. That may be a nice workaround, 
and the better way to go for you.


Cheers,

Thomas Goirand (zigo)