On Saturday 20 September 2008 06:01:52 Johannes Berg wrote: > iw was intended to be put into /usr/bin but aircrack-ng ships a version > in /usr/sbin/, see bug 499246
Indeed, I added a Conflicts: aircrack-ng to the debian/control file because of this when preparing the package this afternoon. What aircrack-ng is doing makes iw look bad for breaking policy: Section 2.5 Priorities "Note that optional packages should not conflict with each other." Bad aircrack maintainer :) Once the bastard iw is removed from aircrack-ng, the Conflicts field can have a version conditional added to it. On a side note, iwconfig is currently installed to /sbin (and it doesn't link with anything on /usr/), as I understand it is there so that it may be used to configure a network device early in boot so that a network filesystem may be mounted (which might be /usr/). iw seems to make iwconfig redundant in the future. Currently iw links to /usr/lib/libnl.so.X, but if libnl was changed to reside in /lib sometime in the future, I can imagine some people picketing to have iw moved from /usr/bin/ to /bin or /sbin, what is your take on this? Note that i personally think mounting critical network filesystems over wireless to be crazy. Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]