On 27/04/15 17:50, Martin Lucina wrote:
I think including "remote" in the name would be good; it makes it more
obvious that the repo contains tools to "remotely control a rump
something".
If not rumprun-remote (since that implies relation with rumprun-* which is
not true), then how about just rump-remote?
That doesn't a) precisely define what "remote" is b) doesn't convey what
"rump-remote" does. The first one might not be an issue, but the latter
one definitely is. For comparison, a web browser is not called a
html-remote.
I'm sort of tempted to suggest rump-remotecontrol, but I'm not sure if
that reminds me more of Leisure Suit Larry 1 or one very old "How to
speak Australian" commercial.
Why is it necessary to emphasize remote, i.e. why are you worried that
someone might confuse it for controlling "opposite of remote"?
