Ben Finney <bign...@debian.org> writes:
> self-contained program.
> Such programs are designed, by their authors, to be downloaded to a
> directory and loaded from there into the user's choice of browser.
An example of such a work is “MuscleBook”, which “has no server and
works completely offline” <URL:https://github.com/cfilipov/MuscleBook.net>.
> To package such a program for Debian – into a hypothetical Debian
> binary package ‘ipsum’ – I expect that installing that package will
> give a command-line executable program, which launches and runs.
So, I would expect after installing the hypothetical ‘musclebook’ Debian
package, that a command such as ‘/usr/bin/musclebook’ is installed.
Then, running ‘/usr/bin/musclebook’ at the command line invokes a new
browser tab (or a new browser window is started) visiting the MuscleBook
I understand how to install the files (to ‘/usr/share/musclebook/’, for
example). What comes next is to work correctly with the Debian web
browser convention, and have a command-line program load the file
‘/usr/share/musclebook/index.html’ in the currently-running browser.
How would a Debian package do that nicely with our conventions?
\ “But it is permissible to make a judgment after you have |
`\ examined the evidence. In some circles it is even encouraged.” |
_o__) —Carl Sagan, _The Burden of Skepticism_, 1987 |