You can also use the command "stack path --local-install-root" to find out where stack puts the executable. If that directory is "/foo", then you'll find the snap executable at /foo/bin/snap. You can then copy it to a directory that is in your PATH or you can run it directly from there.
On Thu, Jul 28, 2016 at 6:01 AM, Sönke Hahn <[email protected]> wrote: > stack by default doesn't install the executables of dependencies somewhere > in your PATH. You could try to use > > $ stack exec -- snap ... > > `stack exec` should make the executables available. > > HTH, > Sönke > > On Thu, Jul 28, 2016 at 11:18 AM, kees Bleijenberg > <[email protected]> wrote: >> >> I'am using stack. I've add snap to the 'build-depends' in the cabal file. >> Then I did stack build and stack installs snap. >> Now commands like snap init barebones fail. I think it is because snap >> doesn't know the stack structure. Is the combination snap stack invalid? >> >> Kees >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Snap Framework" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. > > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Snap Framework" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- --- You received this message because you are subscribed to the Google Groups "Snap Framework" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
