Wookey <woo...@wookware.org> writes: > +++ Raphael Hertzog [2012-03-29 21:06 +0200]: >> Hi, >> >> On Thu, 29 Mar 2012, Wookey wrote: >> > Anyone know when this happened and what if any, the limitations are? >> > It's certainly true in wheezy, squeeze, precise and oineiric. >> >> This has always been the case ever since dpkg-architecture has been >> introduced. > > OK, shows how much I know :-) > >> But you should not rely on this because calling debian/rules directly >> must be supported. > > Hmm, but if a package cannot use the variables set by > dpkg-buildpackage and must set them itself, what is the point of > dpkg-buildpackage setting them? To save the package exporting the > variables?
There is no point. Packages must use dpkg-architecture, dpkg-buildflags,... or the respective makefile sniplets in /usr/share/dpkg/ in case debian/rules is called directly, they must not rely of dpkg-architecture setting them. Hopefully dpkg-buildpackage will stop setting those varibales at some point so sources that wrongfully depend on the variables being set actualy break. MfG Goswin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87398q9s9g.fsf@frosties.localnet