** Description changed: - As .snap package costs a lot of space we need ability to store it on + As .snap package costs a lot of space so we need ability to store it on removable drives. But it's impossible to run they from there. Only way to run .snap is to mount it running "sudo snap install --dangerous <.snap location>" command, that copy package into '/var/lib/snapd/snaps' and maybe do some other things. In theory, it's need to be '(sudo if need) snap run *--dangerous <.snap location>*' here, that will temporary create symlink to my .snap in '/var/lib/snapd/snaps', mount and then run it. If there is many apps in one package, it’s can be done to have exceptions for "one app" .snap’s and for .snap’s that have "main_application: *app name here*" in snapcraft.yaml. Otherwise "Cannot run, this package contains many applications and don't have a "main_application" option defined. Install it instead? [Y/n]" message should be displayed.
** Description changed: As .snap package costs a lot of space so we need ability to store it on - removable drives. But it's impossible to run they from there. Only way + removable drives. Now it's impossible to run they from there. Only way to run .snap is to mount it running "sudo snap install --dangerous <.snap location>" command, that copy package into '/var/lib/snapd/snaps' and maybe do some other things. In theory, it's need to be '(sudo if need) snap run *--dangerous <.snap location>*' here, that will temporary create symlink to my .snap in '/var/lib/snapd/snaps', mount and then run it. If there is many apps in one package, it’s can be done to have exceptions for "one app" .snap’s and for .snap’s that have "main_application: *app name here*" in snapcraft.yaml. Otherwise "Cannot run, this package contains many applications and don't have a "main_application" option defined. Install it instead? [Y/n]" message should be displayed. ** Description changed: - As .snap package costs a lot of space so we need ability to store it on + As .snap package costs a lot of space we need ability to store it on removable drives. Now it's impossible to run they from there. Only way to run .snap is to mount it running "sudo snap install --dangerous <.snap location>" command, that copy package into '/var/lib/snapd/snaps' and maybe do some other things. In theory, it's need to be '(sudo if need) snap run *--dangerous <.snap location>*' here, that will temporary create symlink to my .snap in '/var/lib/snapd/snaps', mount and then run it. If there is many apps in one package, it’s can be done to have exceptions for "one app" .snap’s and for .snap’s that have "main_application: *app name here*" in snapcraft.yaml. Otherwise "Cannot run, this package contains many applications and don't have a "main_application" option defined. Install it instead? [Y/n]" message should be displayed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711847 Title: "snap run" doesn't support not installed packages To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1711847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
