Conversation

Notices

1. Embed this notice
   Perma (prma@fosstodon.org)'s status on Friday, 28-Jun-2024 17:58:53 JST Perma

   • SuperDicq

   @SuperDicq for some reason, I had to build my rust binaries through nix-flake and then rsync -> ssh -> supervisorctl reboot
   Because my hosting did not provide updated glibc.

   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Friday, 28-Jun-2024 17:58:53 JST SuperDicq

     in reply to

     @prma@fosstodon.org That sounds absolutely insane

   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Friday, 28-Jun-2024 18:07:53 JST SuperDicq

     in reply to

     @prma@fosstodon.org Since it's your code better solution just be to add backwards compatibility to your code so it works with older glibc?

   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Friday, 28-Jun-2024 18:12:01 JST SuperDicq

     in reply to

     @prma@fosstodon.org Also why do you need to build a nix flake for this? You could just compile your code with static linking instead?

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 28-Jun-2024 18:15:13 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • SuperDicq
     @SuperDicq @prma Or you know, static binaries… Oh wait glibc :DDD
   • Embed this notice
     Perma (prma@fosstodon.org)'s status on Friday, 28-Jun-2024 18:19:36 JST Perma

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • SuperDicq

     @lanodan @SuperDicq usually musl target takes care of that, in this case, however, it needed more build-time dependencies.

   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Friday, 28-Jun-2024 18:19:36 JST SuperDicq

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @prma@fosstodon.org @lanodan@queer.hacktivis.me I feel like only Rust has this issue

   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Friday, 28-Jun-2024 18:26:39 JST SuperDicq

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @prma@fosstodon.org @lanodan@queer.hacktivis.me Python's dependency management is actually insane.
     
     "yeah just parse our requirements.txt file with pip"
     "actually its better if you use pipx for that one"
     "no wait actually just use anaconda makes an even bigger mess
     
     They said Python would become better after Python 2 got deprecated.

   • Embed this notice
     Perma (prma@fosstodon.org)'s status on Friday, 28-Jun-2024 18:26:40 JST Perma

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • SuperDicq

     @SuperDicq @lanodan I only had to deal with Go and Rust and Python. Go is relatively extremely simpler, but also more isolated.
     But I take dependency issues of Rust's over Python's, any day!

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 28-Jun-2024 18:33:49 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • SuperDicq
     @SuperDicq @prma Which is why here Python libs are installed using the system package manager, then maybe PYTHON_PATH later for things like dependencies that aren't released yet.
     
     pip is never gonna be on my machines, it's a complete disaster. For example it always executes setup.py, and no not everyone migrated to pep517 yet).
     Then you have PyPI allowing completely random archives including compiled code, no idea if you can even disable that. And quite few times I've seen it fail to resolve dependencies on other people's machines…
   • Embed this notice
     Perma (prma@fosstodon.org)'s status on Friday, 28-Jun-2024 18:46:43 JST Perma

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • SuperDicq

     @lanodan @SuperDicq talking about the package managers, NixOS packages that usually break in Nixpkgs unstable, usually are python ones. And when something like kernel's build starts breaking, and I look into it, I see a python script in the build process that added a dependency for some reason. And now tests are not passing.
     I'm getting worked up as I'm saying this.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 28-Jun-2024 18:46:43 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • SuperDicq
     @prma @SuperDicq Fun, never had that in 8+ years of using gentoo. :D
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 28-Jun-2024 19:00:34 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • SuperDicq
     @prma @SuperDicq Possibly, that said while I keep on using stabilized recipes as default I have quite a lot of software using unstable, including python libraries.
     
     Plus gentoo doesn't do whole-tree stabilization (which would involve freezes) but per-packages ones. Yet somehow broken recipes are mostly due to more or less abandoned software (like video games where the last release was ~15 years ago).
   • Embed this notice
     Perma (prma@fosstodon.org)'s status on Friday, 28-Jun-2024 19:00:35 JST Perma

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • SuperDicq

     @lanodan @SuperDicq might that be because gentoo people are taking care of it before reaching stable?

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 28-Jun-2024 20:30:03 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • SuperDicq
     • Reid :ablobcatattention:
     @Reiddragon @prma @SuperDicq Oh so that's why people these days are going "Yes, please destroy my system" when pip is involved.
     
     Wasn't much of a bad idea to allow protection of the stuff in /usr/lib/ (although… why? People who go cowboy as root reap what they sow) but well… terrible execution if it messes with other installation dirs.
   • Embed this notice
     Reid :ablobcatattention: (reiddragon@fedi.reimu.info)'s status on Friday, 28-Jun-2024 20:30:04 JST Reid :ablobcatattention:

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • SuperDicq
     @SuperDicq @lanodan @prma tbh it onpy got worse as of late, especially with pip acting like ~/.local/lib is managed by the system package manager
   • Embed this notice
     Reid :ablobcatattention: (reiddragon@fedi.reimu.info)'s status on Friday, 28-Jun-2024 20:40:57 JST Reid :ablobcatattention:

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • SuperDicq
     @lanodan @prma @SuperDicq tbh using ~/.local/ is perfectly acceptable for pip, but it conplains that pacman is somehow in charge of the location actually which is just bullshit
     
     and yeah, you have to use the "sure, break the system" flag to make it install stuff anyway
     
     Tbh all I can think is that Python wants pip to be like node's npm with project-local dependencies which is just utter horseshit, there's a reason node_modules is memed to hell as being heavier than a black hole, and it's not because people like it
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 28-Jun-2024 20:43:11 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • SuperDicq
     • Reid :ablobcatattention:
     @Reiddragon @prma @SuperDicq Yet it seems like corporate languages loves this kind of stuff, see Rust, Go, …
     
     (probably because of monorepo brainrot)