• 3 Posts
  • 328 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle













  • Ohai, let’s load our own individual copy of everything separately. Since - we hope - it’s all bult from pristine sources and unlikely to match versions, all that static code load isn’t shared with anything else.

    It’s gonna load slower, take up buckets of space, and not care whether it’s some crusty old thing with sploits aplenty.

    I miss when we had mentors to remind us not only How to be better, but also Why. My mentor was like if obi-wan was born in Dublin. His sarcasm cut deep if you could parse what he was saying.


  • Quick reminder: because flatpak hides your installation state from the system, part of flatpaks could be wildly out of date or toxic releases and your system will.not.care nor even show you anything about it.

    Enterprise tools - or normal stuff that acts like them - that check remotely what you have installed and let you know you’re potentially out of date (like tenable but not junk) will not learn anything about flatpak content.

    Good luck. Every good thing about enterprise packaging is thrown out the window. Flatpaks are toxic.






  • I see from the github ticket you need 3.10 .

    There’s an EPEL clone, apparently, that bundles a python3.10 package.

    MAYBE this is your process:

    yum* install dnf-plugins-core
    yum config-manager --add-repo=https://pkgs.dyn.su/el9/base/x86_64/
    yum install python3.10
    

    Then use it like /usr/bin/python3.10 . Remove it and the repo after.

    *I avoid using DidNotFinish(dnf) even though I know it’s an alias.