[Dune] [#485] dunecontrol doesn't allow options to be passed after the command

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#485 - dunecontrol doesn't allow options to be passed after the command
User who did this - Christian Engwer (christi)

----------
You have to distinguish between options for the command and options for dunecontrol. The --opts option is for dunecontrol and must therefore be passed before the command. This is a common behavior for more complex command line programs, e.g. svn.

This behavior is stated in the dunecontrol documentation:

christi at sansibar:~$ dunecontrol
Usage: dunecontrol [OPTIONS] COMMANDS [COMMAND-OPTIONS]

  Execute COMMANDS for all Dune modules found. All entries in the
  DUNE_CONTROL_PATH variable are scanned recursively for Dune modules.
  If DUNE_CONTROL_PATH is empty, the current directory is scanned.
  Dependencies are controlled by the dune.module files.

OPTIONS:
  -h, --help         show this help
      --debug        enable debug output of this script
      --module=mod   only apply the actions on module mod
                     and all modules it depends on
      --only=mod     only apply the actions on module mod
                     and not the modules it depends on
      --current      only apply the actions on the current module,
                     the one in whichs source tree we are standing
      --opts=FILE    load default options from FILE
                     (see dune-common/doc/example.opts)
      --[COMMAND]-opts=opts   set options for COMMAND
                     (this is mainly useful for the all COMMAND)
COMMANDS:
  Colon seperated list of commands. Availabel commands are:
  `help'	guess what :-)
  `print'	print the list of modules sorted after their dependencies
  `update'	updated all modules from the repository
  `autogen'	run the autogen.sh script for each module
  `configure'	run configure for each module
  `make'	run make for each module
  `all'		run 'autogen', 'configure' and 'make' command for each module
  `exec'	execute an arbitrary command in each module directory
  `status'	show vc status for all modules
  `svn'		run svn command for each svn managed module
  `export'	run eval `dunecontrol export` to save the list of
  		dune.module files to the DUNE_CONTROL_PATH variable

----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=485#comment703

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.