On Sat, Oct 24, 2009 at 08:51:57PM +0300, Modestas Vainius wrote: > On sekmadienis 16 Rugpjūtis 2009 12:02:47 Colin Watson wrote: > > This seems like the natural way to use a buildsystem, but it breaks: > > > > #! /usr/bin/make -f > > %: > > dh -Bbuild $@ > > > > This is of course because, unless it's been told about the -B option by > > buildsystems_init, Dh_Getopt parses this as -B -b -u=ild. > > > > Both '-B=build' and '-B build' break in different ways; '-B=build' tries > > to use a build directory called '=build', while 'dh -B build clean' does > > nothing. '--builddirectory=build' works, though. > > > > I don't know whether this is fixable without breaking other things. If > > not, maybe this gotcha could at least be documented. > > When you want to proxy options down to other debhelper commands via dh, it is > recommended to have the following in mind: > > 1) Do NOT use short options (esp. with arguments). Since bundling is enabled, > this is prone to errors. What is more, several debhelper commands are more > likely to understand the same short option but for different purposes.
Would it be a bad idea (and if so, why) to simply educate all debhelper commands about -B, -D, and -S by default, making them no-ops? Nothing in the core command set, at least, seems to do anything else with them, although I haven't checked the external debhelper plugins in the archive. There seems at least a fairly decent chance that this would cause no practical problems. I understand the general problem, and I can see that it may well be best to just document it and live with it, but the buildsystem options are ones that are commonly proxied through dh and it would be nice to make it as easy as possible to do so. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
