Inconsistent naming/usage for ghcjs-options?

I just noticed that when I specify `ghc-options` in a `.cabal` file for a ghcjs project, these options are passed to the `ghcjs --make` execution during the build.

But when I pass `cabal build --ghc-options=...`, those options are not passed to it; instead I need to use `cabal build --ghcjs-options=...`.

This seems inconsistent to me, and puts me into a situation where the Cabal file format and the cabal command line flags work differently.

Is this an oversight or intended?