Re: Bug#825161: blends-dev: please introduce something like compat level

On Fri, Mar 23, 2018 at 11:55:09PM +0100, Ole Streicher wrote: > >> Could you tell me whether this fits your needs here? > > > > Fine for me > > The format line would suggest that the version of our manual can be > found there. So, would you mind to create a copy so that the current > version

Re: Bug#825161: blends-dev: please introduce something like compat level

Hi Andreas, Andreas Tille writes: > On Fri, Mar 23, 2018 at 11:59:15AM +0100, Ole Streicher wrote: >> When this field is there, it is interpreted as format version, and the >> code can take care of different formats. In the moment, it distinguishes >> here between downgrading

Bug#825161: blends-dev: please introduce something like compat level

Hi Ole, On Fri, Mar 23, 2018 at 11:59:15AM +0100, Ole Streicher wrote: > When this field is there, it is interpreted as format version, and the > code can take care of different formats. In the moment, it distinguishes > here between downgrading the dependency level (for format < 1.1) and >

Bug#825161: blends-dev: please introduce something like compat level

Control: tag -1 pending Hi Holger, I am going to re-write the blends-gen-control utility in blends-dev in Python 3: https://salsa.debian.org/olebole/python-debian-blends (preliminary development repository; will merge into the blends package). This utilizes an optional field "Format" in the

Bug#825161: blends-dev: please introduce something like compat level

package: blends-dev severity: wishlist version: 0.6.16.2 Hi, debhelper uses a nice thing called compat level, which has to be set in each source package. So if compat is set to 9, $these features are enabled, and if compat is set to 10, $these features *and* $those are enabled. (eg dbgsym