I disagree that it's invalid—design doctrine number 1: it's *never* the user's fault.
After installing *any* other package, you can run it by invoking the package's name. Exceptions, such as ImageMagick, print usage instructions instead.
The user (me) has no way of knowing that they should invoke the software using a command other than the package name.
What rationale is there for deviating so strongly from the usual behaviour?
I think the user not being able to even *start* the program, because the method to run it is non-standard and completely undiscoverable, is a valid design bug.
Because of this, I'm reopening the bug. If you genuinely intend that the user shouldn't be able to figure out how to run the software they've just installed, then by all means, please re-close it.
I disagree that it's invalid—design doctrine number 1: it's *never* the user's fault.
After installing *any* other package, you can run it by invoking the package's name. Exceptions, such as ImageMagick, print usage instructions instead.
The user (me) has no way of knowing that they should invoke the software using a command other than the package name.
What rationale is there for deviating so strongly from the usual behaviour?
I think the user not being able to even *start* the program, because the method to run it is non-standard and completely undiscoverable, is a valid design bug.
Because of this, I'm reopening the bug. If you genuinely intend that the user shouldn't be able to figure out how to run the software they've just installed, then by all means, please re-close it.