It would help me evolve without stopping me from evolving, if you test and give feedback on a program that I implemented called am-okay.
It is a program that partly imitates the Linux cp command but dynamically. The use of the program itself partly reflects how to copy/cut files/directories in a graphical environment and paste them where access is permitted, but it goes beyond that (once the program is installed run the Linux command man am-okay to see all the possible actions with the current version of the program) .
You can either install it directly (of course after downloading it) via dpkg or install it via this package manager that I implemented which is located on the same Gihub repository (its name is meo) .
I would also like to know if such a program deserves classic confinement or not on snap.
Be free to express yourself (I like criticism , especially if it is informed).
I won’t be testing the applications, but I had a quick look. I note it’s a zsh shell script. The snap core doesn’t bundle zsh, but does bundle bash. So if you’re making a snap of am-okay, you’ll need to bundle zsh. Here’s a sample yaml, which I have not tested. It assumes the shell script am-okay is in snap/local/bin
But for man and info, I think that this would require an understanding with the founders or senior managers of snap.
By defining by default a general database for any snap program, it would be possible to insert files written in groff or troff (file format compatible with man and info) in this last. In this sense we could display the program documentation by executing for example a command like: snap man my-snap-program