Re: Optional Build-Depends

2020-07-16 Thread Julian Andres Klode
On Thu, Jul 16, 2020 at 06:56:56PM +0100, Steve McIntyre wrote: > > On Thu, Jul 16, 2020 at 07:27:52PM +0200, Julian Andres Klode wrote: > > ... > > >Rationales: > > > > > >1. You can start optionally build-depending on stuff available > > only on some architectures, without having to use

Re: Optional Build-Depends

2020-07-16 Thread Johannes Schauer
Hi, Quoting Julian Andres Klode (2020-07-16 19:27:52) > Rationales: > > > 1. You can start optionally build-depending on stuff available >only on some architectures, without having to use arch restriction >lists. > >Arch restriction lists are tediuous, especially also because in >

Re: Optional Build-Depends

2020-07-16 Thread Steve McIntyre
On Thu, Jul 16, 2020 at 07:27:52PM +0200, Julian Andres Klode wrote: ... >Rationales: > > >1. You can start optionally build-depending on stuff available > only on some architectures, without having to use arch restriction > lists. > > Arch restriction lists are tediuous, especially also

Re: Optional Build-Depends

2020-07-16 Thread Julian Andres Klode
On Thu, Jul 16, 2020 at 07:27:52PM +0200, Julian Andres Klode wrote: > Not liked proposals: > > Build-Depends-Optional field - it would just be ignored by tools, > silently, and we'd find about it onyl when it is too late. > > Build-Recommends field - same as previous, but also the

Optional Build-Depends

2020-07-16 Thread Julian Andres Klode
Hi, we were just talking in #debian-dpkg about optional build-deps. guillem believes that the release team is in the best position to specify if this is reasonable or not, so here we go: We have came up with a syntax, one goal being to break parsers and not silently ignore optional deps: