Bug#747875: ben: position of --config argument matters

[Johannes Schauer <j.schauer@email.de>]

Hi,

Quoting Mehdi Dogguy (2014-05-12 20:28:17)
> Le 2014-05-12 16:39, Johannes Schauer a écrit :
> > Package: ben
> > Version: 0.6.11
> 
> This version is not released yet. The BTS should be confused now :)

whoops, sorry. As you can imagine that happened because I had ben packages
compiled from git installed.

> Yeah, and it doesn't look like a surprise, at least for me. A .ben file
> should be considered as way to put command-line options into a file. So in
> your example, "--config test.ben" is equivalent to "--archs armel".  Hence
> the described result.

I usually expect that configuration file values can be overwritten by command
line arguments. Naturally ben's way of interpreting the --config argument makes
sense as well but then I'd argue that it should be documented.

Classical case of: it's not a bug, it's a feature! :)

cheers, josch