2017-08-23 8:50 GMT+02:00 Ben Finney <[email protected]>: > Ben Finney <[email protected]> writes: > > > I am interested in packaging for Debian some JavaScript code that is a > > 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 > ‘index.html’. > > 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? >
xdg-open <filepath> ? Jérémy
-- Pkg-javascript-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
