/usr/bin/fold got permission denied but /usr/bin/fmt is working fine. What's happened?

[Zoralab]

@ogra

there should be no need to as long as you use snapcrafts “apps” entry … this auto-generates a wrapper with a PATH entry pointing to $SNAP/bin, $SNAP/usr/bin etc etc … … this indeed gets hairy if your binary usees full paths (which it shouldnt if you want to write portable code))

Yeap. If we use the apps entry, it will expose the fold as an app externally. In some situation, we might not want it. No worries, I can still live with $SNAP variables for time being.

---

@ogra

in case you want more complex setups you can also take a look at the experimental layouts feature …

Thanks for sharing !

passthrough is definately new and came to realize, I’m on the bleeding edge. Reading through:

1. Support for passthrough into snap.yaml - #6 by niemeyer
2. https://snapdocs.labix.org/snapcraft-yaml-reference/4276

---

@Lin-Buo-Ren

Just stage the executable is enough as in the runtime PATH="$SNAP/usr/sbin:$SNAP/usr/bin:$SNAP/sbin:$SNAP/bin:$PATH"

That’s definitely a way but it will create extra documentation step and exhibits enough complexity for packaging process. These 2 are enough to say a packager had failed its manifesto. By ideal user experience, we should always restrict the amount of user action to 1 and only:

$ snap install <software>

The rest are packager’s job.

---

@jdstrand

FYI, I’ll add fold in the the next batch of updates, but in the meantime, you need to ship it in your snap.

Thank you! Am already editing 1.3.1 release to use fmt. No hush.