On Sat, 2009-05-02 at 16:50 -0400, Frédéric Brière wrote: > On Sat, May 02, 2009 at 09:33:57PM +0100, Adam D. Barratt wrote: > > This might be losing something in translation. :-) Given that > > licensecheck is a command line tool, how can those options /not/ "be > > applied to the command line"? > > I should've specified: for each non-directory command line argument. > > I would draw a parallel with ls(1): if I type "ls" or "ls <dir>", I > expect that some entries in <dir> will be ignored by default. However, > if I explicitly ask "ls .bashrc", I now expect that file to be listed, > with or without "-a".
I understand what you mean, and can see the logic. However, the parallel doesn't quite map, as "licensecheck" on its own currently gives usage instructions, rather than being equivalent to "licensecheck .". My concern is whether people currently expect "licensecheck *" on a directory containing many files to actually inspect every single file or only those which match the default regex. If the expectation is the latter then I'm not sure where to go from there, given that the script can't tell the difference between you calling "licensecheck *" and "licensecheck filea fileb filec ... filezz". Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
