!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

186 Members
55 Servers

Load older messages


SenderMessageTime
2 Oct 2025
@pyrox:pyrox.devdish [Fox/It/She]* but not if its unmaintainable like nodePackages is atm04:58:56
@winter:catgirl.cloudWinterdisagree, 99.9999% of things that were shoved into nodePackages were applications, which belong at the top level05:01:53
@sandro:supersandro.deSandro 🐧yep, it was a maintenance nightmare and regularly all kinds of things broke left, right, center and between14:19:46
@marie:marie.cologneMarieor you regenerated the thing and in the meantime someone updated it and you had to regenerate it again14:21:05
@hexa:lossy.networkhexa Winter: frankly, nodePackages should have received a staggered response with milestones 14:38:49
@hexa:lossy.networkhexa
  • trace warnings 24.05
  • broken or something equally annoying 25.11
  • removed in 26.05
14:39:30
@hexa:lossy.networkhexaand I hope we can achieve these things with nixpkgs core14:39:40
@hexa:lossy.networkhexanodePackages still exists because we're not good at long term consistent decison making14:40:17
@hexa:lossy.networkhexabut we can't even issue trace warnings, because the ci folks decided we may not14:41:45
@hexa:lossy.networkhexamodules may, packages may not14:42:25
@c0ba1t:matrix.orgCobalt How are package removals communicated then? Let's say I depend on libfoo and it gets removed (no maintainer, no dependents), wouldn't a warning be a good idea then? 14:44:05
@winter:catgirl.cloudWinter🙃14:44:10
@winter:catgirl.cloudWintera throw14:44:16
@c0ba1t:matrix.orgCobalt Throw as in "package not found"? 14:44:32
@hexa:lossy.networkhexathrow as in "lol, its too late"14:47:43
@hexa:lossy.networkhexabecause we don't ship this package anymore14:47:57
@hexa:lossy.networkhexait was yanked14:48:01
@hexa:lossy.networkhexafoo = throw "foo was removed from nixpkgs, because it was utter garbage"14:48:13
@hexa:lossy.networkhexa *
foo = throw "foo was removed from nixpkgs, because it was utter garbage";
14:48:16
@pyrox:pyrox.devdish [Fox/It/She] still does, its a pain to fix merge conflicts when i have multiple PRs in flight against it 🥴 14:55:59
@sandro:supersandro.deSandro 🐧The best way out of that is to extract the packages from it14:57:11
@sandro:supersandro.deSandro 🐧* The best way out of that is to extract the packages from it you care about14:57:16
@pyrox:pyrox.devdish [Fox/It/She]yeah that's what I'm doing14:57:18
@pyrox:pyrox.devdish [Fox/It/She]but its a pain even when doing that for multiple packages in parallel14:57:29
@sandro:supersandro.deSandro 🐧Just removing the package should no require a regen and have little conflicts14:57:43
@pyrox:pyrox.devdish [Fox/It/She]oh gods i never regen the set14:59:45
@pyrox:pyrox.devdish [Fox/It/She]that's never gonna happen if i can help it15:00:04
@pyrox:pyrox.devdish [Fox/It/She]anything useful can be extracted from it and anything useless gets dropped15:00:16
@pyrox:pyrox.devdish [Fox/It/She]might make a mega-PR removing all packages from nodePackages that are currently unpackagable due to not having upstream lockfiles15:01:05
@pyrox:pyrox.devdish [Fox/It/She]* might make a mega-PR removing all packages from nodePackages that are currently unpackagable in normal nixpkgs expressions due to not having upstream lockfiles15:01:51

Show newer messages


Back to Room ListRoom Version: 6