On Wed, Sep 11, 2002 at 10:02:21PM +0200, Yann Dirson wrote: > I couldn't find in policy 3.5.7.0 any requirement that would allow an > autobuilder to know it should call "debian/rules build-arch" instead > of "debian/rules build", prior to call "fakeroot debian/rules binary-arch". > > I thought (as outlined in a related bugreport, although my words in > this report were a bit confused) that the policy should have made the > binary-arch target mandatory, so that the atobuilders could know from > the declared standard-version whether the target was expected or not. > > Currently it seems the autobuilders will have either to parse the > rules file, or to attempt to use build-arch and parse the output if > that failed - none of these alternatives seem reasonable to me.
There was a long flame^Wdiscussion a while back about the possibility of doing something like the following: ret=$(set +e; debian/rules -q build-arch >/dev/null 2>&1; echo $?) if [ $ret -eq 2 ]; then debian/rules build else debian/rules build-arch fi This presumes that debian/rules understands the -q convention and gives the same exit codes as make does. This will be the case if debian/rules is a makefile, but if not.... [ducks and runs for cover!] Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London website: http://www.maths.qmul.ac.uk/~jdg/ Debian GNU/Linux Developer, see: http://people.debian.org/~jdg/ Visit http://www.thehungersite.com/ to help feed the hungry