Bug#913816: dpkg-dev: dpkg_vendor_derives_from documentation produces wrong results

2018-12-02 Thread Guillem Jover
On Sun, 2018-11-25 at 21:03:32 -0500, Jeremy Bicha wrote: > Yes, I would appreciate a less cumbersome way of checking the build > vendor than what we have now. > > One package that makes fairly extensive use of dpkg-vendor is gnome-software: > >

Bug#913816: dpkg-dev: dpkg_vendor_derives_from documentation produces wrong results

2018-11-25 Thread Jeremy Bicha
Yes, I would appreciate a less cumbersome way of checking the build vendor than what we have now. One package that makes fairly extensive use of dpkg-vendor is gnome-software: https://salsa.debian.org/gnome-team/gnome-software/blob/debian/master/debian/rules#L45 Thanks, Jeremy Bicha

Bug#913816: dpkg-dev: dpkg_vendor_derives_from documentation produces wrong results

2018-11-15 Thread Guillem Jover
Hi! On Thu, 2018-11-15 at 15:49:08 +, Colin Watson wrote: > Package: dpkg-dev > Version: 1.19.2 > Severity: normal > The header comment in vendor.mk says: > > # The snippet also defines a macro "dpkg_vendor_derives_from" that you can > # use to verify if the current vendor derives from

Bug#913816: dpkg-dev: dpkg_vendor_derives_from documentation produces wrong results

2018-11-15 Thread Colin Watson
Package: dpkg-dev Version: 1.19.2 Severity: normal The header comment in vendor.mk says: # The snippet also defines a macro "dpkg_vendor_derives_from" that you can # use to verify if the current vendor derives from another vendor with a # simple test like this one: # ifeq ($(call