I'm glad it worked :) I need to figure out something for the install problem though, probably will find an other place where the binary can be stored.
On Monday, May 8, 2017 at 11:25:31 PM UTC+2, Rupert Smith wrote: > > On Monday, May 8, 2017 at 8:39:57 PM UTC+1, Rupert Smith wrote: >> >> On Friday, May 5, 2017 at 11:52:09 AM UTC+1, Gusztáv Szikszai wrote: >>> >>> I've been working on this in the last few days, and published 1.0.0 >>> <https://github.com/gdotdesign/elm-github-install/releases/tag/v1.0.0> >>> of *elm-github-install* which handles using a fork (or any other git >>> repository for a package) and using a local directory. If anyone tries this >>> out some feedback would be nice. >>> >> >> I forked another elm package and hacked it, and just want to be able to >> reference it without tagging a release version or publishing. Will be a >> very useful feature I think. I will try it out now, thanks. >> > > Was able to work around the npm installer issue by installing as a ruby > gem instead. Works nicely, and I was able to substitute a branch containing > work in progress - many thanks for these additions to elm-install. :-) > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" 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.
