Re: [elm-discuss] Re: elmvm (Elm Version Manager)
> Looks very clever, not something I had ever looked into before. Do you > have to run NixOS or is nix something that you can run on top of any > distribution? (I'm a long time Debian user). > Nix itself is just a cross-platform package manager, independent of the operating system NixOS. (Though, NixOS is pretty amazing by itself.) https://ocharles.org.uk/blog/posts/2014-02-04-how-i-develop-with-nixos.html is one of the best known introductions I think (but note that Ollie wrote this in 2014). http://ebzzry.io/en/nix/#developmentenvironment might also be a good spot to start. -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [elm-discuss] Re: elmvm (Elm Version Manager)
On Thursday, April 6, 2017 at 6:34:09 PM UTC+1, Rehno Lindeque wrote: > > I'm a little surprised that more people haven't tried nix for pinning > their Elm tools... E.g. pop a shell.nix file like this into your project > root and you'll have it pinned to elm 0.18 indefinitely: > Looks very clever, not something I had ever looked into before. Do you have to run NixOS or is nix something that you can run on top of any distribution? (I'm a long time Debian user). -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [elm-discuss] Re: elmvm (Elm Version Manager)
I'm a little surprised that more people haven't tried nix for pinning their Elm tools... E.g. pop a shell.nix file like this into your project root and you'll have it pinned to elm 0.18 indefinitely: { bootpkgs ? (import {}).pkgs }: let pkgs = import (bootpkgs.fetchFromGitHub { owner = "NixOS"; repo = "nixpkgs"; rev = "6018464c49dc60b1779f10a714974dcb4eb21c30"; sha256 = "1fq9zarsanislnsn9vrn4k852qk1ygckxqdzf1iywgsbp2a5hkn1"; }) { overlays = [ (self: super: let inherit (self) fetchurl fetchFromGitHub callPackage haskell; nodeEnv = callPackage "${self.path}/pkgs/development/node-packages/node-env.nix" {}; in { elmPackages = super.elmPackages // { elm-reactor = haskell.lib.overrideCabal super.elmPackages.elm-reactor (drv: { # I'm using my own fork of elm-reactor that enables ports, because productivity src = fetchFromGitHub { owner = "rehno-lindeque"; repo = "elm-reactor"; sha256 = "0jfhg8gsy3r1myzls5ilx4i87d52lfr05l5736jxvjq926bfv3a2"; rev = "9a1887d60ec3753e25c10084c7ad25f566e5f0a8" ; }; } ); elm-format = haskell.lib.overrideCabal super.elmPackages.elm-format (drv: { src = fetchFromGitHub { owner = "avh4"; repo = "elm-format"; sha256 = "0lman7h6wr75y90javcc4y1scvwgv125gqqaqvfrd5xrfmm43gg8"; rev = "e452ed9342620e7bb0bc822983b96411d57143ef" ; }; postInstall = '' ln -s $out/bin/elm-format-0.18 $out/bin/elm-format ''; } ); elm-oracle = nodeEnv.buildNodePackage { name = "elm-oracle"; packageName = "elm-oracle"; version = "1.1.1"; src = fetchurl { url = "https://registry.npmjs.org/elm-oracle/-/elm-oracle-1.1.1.tgz;; sha1 = "61f6d783221b4ad08e7d101d678b9d5a67d3961c"; }; }; }; } ) ]; }; in pkgs.stdenv.mkDerivation { name = "shell"; version = "0.0.0"; buildInputs = ( with pkgs.elmPackages; [ elm-make elm-package elm-repl elm-reactor elm-format elm-oracle ] ); } As a bonus you can get to add extra goodies like elm-format, elm-oracle, your own personalized fork of elm-reactor or other non-elm tools perhaps (grunt, webpack, nodejs, etc...). Just a thought anyway :) On Thursday, April 6, 2017 at 4:30:02 PM UTC, Nicholas Hollon wrote: > > There needs to be a better advertising of the ecosystem both in terms of >> tools and in terms of packages. >> > > I agree with this, but the effort needs to start with the library authors. > > As far as I can tell (searching this list, Google, & r/elm), Erik is the > only one of these authors who has publicized their work in any way. > > If you invent a wheel, you need to tell people about it. You can't just > leave it lying in your front yard and hope that people walk by your house > :-) > > > > On Thursday, April 6, 2017 at 6:34:53 AM UTC-7, Peter Damoc wrote: >> >> On Thu, Apr 6, 2017 at 3:43 PM, Eirik Sletteberg>> wrote: >> >>> None of these tools are mentioned in the Elm documentation. It only >>> points to installers and the npm module. >> >> >> Exactly my point. >> There needs to be a better advertising of the ecosystem both in terms of >> tools and in terms of packages. >> >> >> -- >> There is NO FATE, we are the creators. >> blog: http://damoc.ro/ >> > -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [elm-discuss] Re: elmvm (Elm Version Manager)
> > There needs to be a better advertising of the ecosystem both in terms of > tools and in terms of packages. > I agree with this, but the effort needs to start with the library authors. As far as I can tell (searching this list, Google, & r/elm), Erik is the only one of these authors who has publicized their work in any way. If you invent a wheel, you need to tell people about it. You can't just leave it lying in your front yard and hope that people walk by your house :-) On Thursday, April 6, 2017 at 6:34:53 AM UTC-7, Peter Damoc wrote: > > On Thu, Apr 6, 2017 at 3:43 PM, Eirik Sletteberg> wrote: > >> None of these tools are mentioned in the Elm documentation. It only >> points to installers and the npm module. > > > Exactly my point. > There needs to be a better advertising of the ecosystem both in terms of > tools and in terms of packages. > > > -- > There is NO FATE, we are the creators. > blog: http://damoc.ro/ > -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [elm-discuss] Re: elmvm (Elm Version Manager)
On Thu, Apr 6, 2017 at 3:43 PM, Eirik Slettebergwrote: > None of these tools are mentioned in the Elm documentation. It only points > to installers and the npm module. Exactly my point. There needs to be a better advertising of the ecosystem both in terms of tools and in terms of packages. -- There is NO FATE, we are the creators. blog: http://damoc.ro/ -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [elm-discuss] Re: elmvm (Elm Version Manager)
None of these tools are mentioned in the Elm documentation. It only points to installers and the npm module. -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [elm-discuss] Re: elmvm (Elm Version Manager)
On Thu, Apr 6, 2017 at 2:00 PM, Richard Woodwrote: > Very healthy having competing options in the ecosystem > :) > > No, this is against Elm philosophy as I understand it. Elm aims to have one, excellent option rather than a plethora of slightly different libraries/tools. The fact that there are so many tools for this simple task is actually indicative of problems in the ecosystem. It seams that people interested in a certain functionality don't find it even if it exists. -- There is NO FATE, we are the creators. blog: http://damoc.ro/ -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [elm-discuss] Re: elmvm (Elm Version Manager)
Very healthy having competing options in the ecosystem :) -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[elm-discuss] Re: elmvm (Elm Version Manager)
Checkout out https://github.com/rtfeldman/elm-use as well. I believe it serves a similar purpose. On Wednesday, April 5, 2017 at 7:33:45 AM UTC-7, Eirik Sletteberg wrote: > > https://github.com/eirslett/elmvm > > This is a simple utility inspired by nvm (Node Version Manager). > It lets you install and manage multiple versions of Elm on the same > machine, and switch between them easily. > > -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[elm-discuss] Re: elmvm (Elm Version Manager)
Thanks so much, this is really useful! I've have quite a few projects that are in different versions of Elm, and migrating them all en-masse to the latest version is always a chore. It will be great to go back and an compile them in 0.17 and 0.16 again! :) -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.