David Adler wrote: > [snip] > It would be better to just list jack_snapshot > as a dependency, requiring users to install it > separately before using the script. > > Reasons: > > Most users won't want - or do not have the > permissions - to run a script as a root. > > Since Installation of dependencies only needs > to be done once while script is run often it > is good habit to separate installation from > applications. >
I do agree. Another issue might be to use CLI arguments e.g. "sh obsession store", "sh obsession restore" instead of that wannabe ncurses style, BUT I'm not seriously thinking that this script might be interesting for other users, I'm writing it to learn about POSIX shell scripts. Btw. I wonder if this is POSIX: http://www.linuxjournal.com/article/2807 > for Alsa: > aconnect -i and aconnect -o > > for Jack (audio and Jack-Midi): > jack_lsp > > > Some more general thoughts: > > The concept of storing and restoring a session > by a script has its limitations: > > Well written (most) applications can be started > from the command line with options that allow > to exactly restore a prior state. > > IMHO running applications cannot be queried > about all those options via command line. > > So restoring a session by a script is perfectly > possible. In terms of storing a session, a > script would be rather weak. > > What a script could do is save a template > script from a set of interconnected applications. > The user then could manually fix and extend > that template and use it as a startup script. > Just an idea that came to me. Thank you David :). Ralf _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
