Hah, well that has to be one of my shortest-lived changes ever. But as long as I can `fetchgit (importSomehow ./src.json)` I'll be happy, and it seems pretty useful to have nix understand JSON quite well anyway, since it's so pervasive. Thanks for publicising this, zimbatm :)
Cheers, - Tim. On Mon, Feb 29, 2016 at 5:55 AM, zimbatm <[email protected]> wrote: > Interesting how much traffic this thread has. If we have importJSON I > suppose that we could then output JSON from all of our tooling. It should > also make it easier to get the output from any modern language. > > In that case I will make some changes so that nix-prefetch-git outputs JSON > by default and propose importJSON to be added to the stdlib. > > On Sun, 28 Feb 2016 at 17:48 Moritz Ulrich <[email protected]> wrote: >> >> >> zimbatm <[email protected]> writes: >> > ``` >> > $ nix-prefetch-git git://github.com/direnv/direnv.git 2>/dev/null | tee >> > repo.nix >> > { >> > url = "git://github.com/direnv/direnv.git"; >> > rev = "9283a67646349bfef002a7242db47a6b8ef75305"; >> > sha256 = "15kbzxwl03f0awnf5n6mw7hcz2dr7p6rpvhfyq3kxn1nk8jxcipx"; >> > } >> > ``` >> >> Any reason why we can't use JSON here? That would make everything *much* >> easier to generate from tools. >> >> I totally agree with other people in this thread: as much as I like Nix >> the language, I don't think we should create another JSON-like data >> format. >> >> Also, The only thange would be putting the attrs in "" and replacing the >> ; with ,. I don't think that would make it less readable. > > > _______________________________________________ > nix-dev mailing list > [email protected] > http://lists.science.uu.nl/mailman/listinfo/nix-dev > _______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
