Thicket data repository for the EEG
anil.recoil.org
1{
2 "id": "https://ryan.freumh.org/2025-03-31.html",
3 "title": "31 Mar 2025",
4 "link": "https://ryan.freumh.org/2025-03-31.html",
5 "updated": "2025-03-31T00:00:00",
6 "published": "2025-03-31T00:00:00",
7 "summary": "<div>\n <span> Previous: <a href=\"2025-03-24.html\">24 Mar 2025</a> </span>\n <span> Next: <a href=\"2025-04-07.html\"> 7 Apr 2025</a> </span>\n </div>\n \n \n\n <ol>\n<li><p><span><span>X</span> Wrote <a href=\"https://tangled.sh/@ryan.freumh.org/caledonia\">Caledonia</a>, a\nCommand-line Calendar Client</span></p></li>\n<li><p><span><span>X</span> There’s been\nrenewed interest in upstreaming my <a href=\"https://github.com/ocaml/opam/pull/5982\">NixOS depext mechanism\nfor Opam</a>, which creates a Nix environment which Opam manages to\nprovide system dependencies, and was one of the original ideas behind <a href=\"./enki.html\">Enki</a>, so I’ve been polishing that up this\nweek.</span></p></li>\n<li><p><span><span>X</span> I deployed the\n<a href=\"https://repology.org/\">repology</a> database locally and got\nsome queries working on it. It’s a great data source, and will hopefully\nbe useful in ‘unifying’ packages present in multiple ecosystems using <a href=\"https://github.com/repology/repology-rules\">repology’s\ndeduplication rules</a>.</span></p>\n<p><span>It doesn’t contain rich metadata for packages,\nthough. It scrapes sources of data for package names and versions (e.g.\nOpam’s <a href=\"https://opam.ocaml.org/json/stats.json\">https://opam.ocaml.org/json/stats.json</a>,\nNix’s <a href=\"https://channels.nixos.org\">https://channels.nixos.org</a>, and\nDebian’s <a href=\"https://ftp.debian.org/debian/dists/\">https://ftp.debian.org/debian/dists/</a>,\nthrough <a href=\"https://github.com/repology/repology-updater/\">https://github.com/repology/repology-updater/</a>).\nSo it doesn’t have metadata like Opam package authors (nevermind\ndependency constraints).</span></p></li>\n<li><p><span><span>X</span> While looking\ninto repology I found their <a href=\"https://github.com/repology/libversion-rs\">Rust libversion</a>\nimplementation, which could be useful to replace my <a href=\"https://github.com/RyanGibb/enki/blob/main/enki_solver/src/version.rs\">version\nimplementation</a>, but I’m not sure if it’s</span></p></li>\n<li><p><span><span>X</span> I read <a href=\"https://bernsteinbear.com/blog/nix-by-hand/\">Nix by Hand</a>,\nwhich got my thinking about how <a href=\"enki.html\">Enki</a> could\ninteract with the Nix store without going through Nix\nexpressions.</span></p>\n<p><span>The Nix ecosystem appears to be experiencing a bit\nof a cambrian explosion at the moment so this is something to keep an\neye on with all the alternative implementations going about. Watch <a href=\"https://github.com/NixOS/rfcs/pull/134/\">RFC 0134 Carve out a\nstore-only Nix</a> and the <a href=\"https://github.com/NixOS/nix/issues/7868\">Tracking issue for RFC\n134.</a> Also see the <a href=\"https://github.com/haskell-nix/hnix-store\">Haskell Nix\nStore</a>.`</span></p></li>\n</ol>",
8 "content": "<div>\n <span> Previous: <a href=\"2025-03-24.html\">24 Mar 2025</a> </span>\n <span> Next: <a href=\"2025-04-07.html\"> 7 Apr 2025</a> </span>\n </div>\n \n \n\n <ol>\n<li><p><span><span>X</span> Wrote <a href=\"https://tangled.sh/@ryan.freumh.org/caledonia\">Caledonia</a>, a\nCommand-line Calendar Client</span></p></li>\n<li><p><span><span>X</span> There’s been\nrenewed interest in upstreaming my <a href=\"https://github.com/ocaml/opam/pull/5982\">NixOS depext mechanism\nfor Opam</a>, which creates a Nix environment which Opam manages to\nprovide system dependencies, and was one of the original ideas behind <a href=\"./enki.html\">Enki</a>, so I’ve been polishing that up this\nweek.</span></p></li>\n<li><p><span><span>X</span> I deployed the\n<a href=\"https://repology.org/\">repology</a> database locally and got\nsome queries working on it. It’s a great data source, and will hopefully\nbe useful in ‘unifying’ packages present in multiple ecosystems using <a href=\"https://github.com/repology/repology-rules\">repology’s\ndeduplication rules</a>.</span></p>\n<p><span>It doesn’t contain rich metadata for packages,\nthough. It scrapes sources of data for package names and versions (e.g.\nOpam’s <a href=\"https://opam.ocaml.org/json/stats.json\">https://opam.ocaml.org/json/stats.json</a>,\nNix’s <a href=\"https://channels.nixos.org\">https://channels.nixos.org</a>, and\nDebian’s <a href=\"https://ftp.debian.org/debian/dists/\">https://ftp.debian.org/debian/dists/</a>,\nthrough <a href=\"https://github.com/repology/repology-updater/\">https://github.com/repology/repology-updater/</a>).\nSo it doesn’t have metadata like Opam package authors (nevermind\ndependency constraints).</span></p></li>\n<li><p><span><span>X</span> While looking\ninto repology I found their <a href=\"https://github.com/repology/libversion-rs\">Rust libversion</a>\nimplementation, which could be useful to replace my <a href=\"https://github.com/RyanGibb/enki/blob/main/enki_solver/src/version.rs\">version\nimplementation</a>, but I’m not sure if it’s</span></p></li>\n<li><p><span><span>X</span> I read <a href=\"https://bernsteinbear.com/blog/nix-by-hand/\">Nix by Hand</a>,\nwhich got my thinking about how <a href=\"enki.html\">Enki</a> could\ninteract with the Nix store without going through Nix\nexpressions.</span></p>\n<p><span>The Nix ecosystem appears to be experiencing a bit\nof a cambrian explosion at the moment so this is something to keep an\neye on with all the alternative implementations going about. Watch <a href=\"https://github.com/NixOS/rfcs/pull/134/\">RFC 0134 Carve out a\nstore-only Nix</a> and the <a href=\"https://github.com/NixOS/nix/issues/7868\">Tracking issue for RFC\n134.</a> Also see the <a href=\"https://github.com/haskell-nix/hnix-store\">Haskell Nix\nStore</a>.`</span></p></li>\n</ol>",
9 "content_type": "html",
10 "categories": [],
11 "source": "https://ryan.freumh.org/atom.xml"
12}