bolha.us

5 posts4 participants0 posts today

スパックマンクリスAm I crazy for considering modifying the <a href="https://twit.social/tags/Mozilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mozilla</a> <a href="https://twit.social/tags/Firefox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Firefox</a> code and recompiling just to get <a href="https://twit.social/tags/emacs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#emacs</a> -like shortcuts? Even just ctrl-s for search and ctrl-w for cut (or at least turning off ctrl-w = close the window) would be huge time savers and "oops" removers.Supposedly there are ways to add some <a href="https://twit.social/tags/javascript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#javascript</a> to dirs to make these changes, but honestly, it seems more difficult than tweaking & recompiling.Seems that extensions can't get deep enough to change some shortcuts.<a href="https://twit.social/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> <a href="https://twit.social/tags/gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gentoo</a>

mgorny-nyan (he) :autism:🙀🚂🐧<a href="https://social.treehouse.systems/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HDF5</a> is doing great. So basically:1. Originally, upstream used autotools. The build system installed a h5cc wrapper which — besides being a compiler wrapper — had a few config-tool style options. 2. Then, upstream added <a href="https://social.treehouse.systems/tags/CMake" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CMake</a> build system as an alternative. It installed a different h5cc wrapper that did not have the config-tool style options anymore. 3. Downstreams that tried CMake quickly discovered that the new wrapper broke a lot of packages, so they reverted to autotools and reported a bug. 4. Upstream closed the bug, handwaving it as "CMake h5cc changes have been noted in the Release.txt at the time of change - archived copy should exist in the history files." 5. Upstream announced the plans to remove autotools support.So, to summarize the current situation:1. Pretty much everyone (at least <a href="https://social.treehouse.systems/tags/Arch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Arch</a>, <a href="https://social.treehouse.systems/tags/Conda" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Conda</a>-forge, <a href="https://social.treehouse.systems/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a>, <a href="https://social.treehouse.systems/tags/Fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fedora</a>, <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a>) is building using autotools, because CMake builds cause too much breakage. 2. Downstreams originally judged this to be a HDF5 issue, so they didn't report bugs to affected packages. Not sure if they're even aware that HDF5 upstream rejected the report. 3. All packages remain "broken", and I'm guessing their authors may not even be aware of the problem, because, well, as I pointed out, everyone is still using autotools, and nobody reported the issues during initial CMake testing. 4. I'm not even sure if there is a good "fix" here. I honestly don't know the package, but it really sounds like the config-tool was removed with no replacement, so the only way forward might be for people to switch over to CMake (sigh) — which would of course break the packages almost everywhere, unless people also add fallbacks for compatibility with autotools builds. 5. The upstream's attitude suggests that HDF5 is pretty much a project unto itself, and doesn't care about its actual users.<a href="https://github.com/HDFGroup/hdf5/issues/1814" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/HDFGroup/hdf5/issues/1814</a>

mgorny-nyan (he) :autism:🙀🚂🐧<a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a> is also going "full <a href="https://social.treehouse.systems/tags/PEP517" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PEP517</a>" now, or to be more precise, we are going to rip out the legacy code paths that used `setup.py install`. However, that doesn't mean that PEP517 support is a solved problem.1. There are still packages that require `setup.py install`, and either outright reject or ignore PEP517. And I'm not talking of dead packages but actively maintained projects. <a href="https://social.treehouse.systems/tags/Fail2Ban" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fail2Ban</a> is a particularly notorious example (the way I see it, it's going to stop working sooner or later).2. Some packages that do work with PEP517 builds, still require some hacks to install correctly. Sometimes it means moving files around, sometimes installing some files manually, sometimes patching stuff.3. There are many packages that use the legacy setuptools backend to workaround their broken PEP517 port. Fortunately, these are at least easy to fix, provided you can convince upstream that actually altering sys.path is the correct solution.4. Finally, we have removed a fair bunch of "hopeless" packages.<a href="https://social.treehouse.systems/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a>

mgorny-nyan (he) :autism:🙀🚂🐧So, if you noticed half a dozen different <a href="https://social.treehouse.systems/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a> compilers being installed on your <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a> system… that's because the eclass pins the compiler to the newest version supported at the time the package was built. So if you built a package when Rust 1.82.0 was the newest version in Gentoo, the package will keep requiring this version until you rebuild it. Move 5 versions forward, and you have random packages pinning half a dozen Rust toolchain versions. Awesome.So what you can do? There's a half-broken 'rust-rebuild' set that will rebuild too many packages (installing all Rust compilers). What you can do instead is, for each old compiler version:1. Determine which package are pinning to it (e.g. via `emerge -cv =rust-1.82.0*`). 2. Check these packages for `RUST_MAX_VER` (optional, but avoids rebuilding stuff that will pin to this version anyway). 3. Rebuild these packages. 4. Try removing the compiler again (`emerge -cv =rust-1.82.0*`). 5. Repeat for every other version till you are left with just the newest.Yeah, Rust is great. Truly love it. [keyboard melted by acid]

mgorny-nyan (he) :autism:🙀🚂🐧Yeah, so if you felt that requiring nightly <a href="https://social.treehouse.systems/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a> compiler to work is not bad enough, we now have packages that call `cargo build` recursively. Like, you build the package and one of the crates calls `cargo build` via `build.rs`. Good news is, is that mostly works.By "mostly", I mean we need to unpack the package first, process Cargo.lock, unpack the crates and then process Cargo.lock from the crates. But who would care about details like that, or that packages are effectively silently fetching more packages behind your back?Memory safety is all that matters! Stable dependencies? Supply chain <a href="https://social.treehouse.systems/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a>? Transparency? Meh, stuff for weaklings!<a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a>

mid_kidInstalling binary packages using the <a href="https://fosstodon.org/tags/portage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#portage</a> package manager feels like watching paint dry, compared to other package managers. I can count multiple seconds per package, even when said package is empty (e.g. a virtual).I've always wondered why that is. It *feels* wrong, and nobody has managed to explain it to me.A few days ago, while waiting multiple hours for 1500 packages to install into a clean root, it finally bothered me enough to dig into it.<a href="https://fosstodon.org/tags/gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gentoo</a> <a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://fosstodon.org/tags/optimization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#optimization</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#python</a>

ParanoidI use <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> with <a href="https://mastodon.social/tags/niri" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#niri</a> window manager and I need a new monitor. Anyone could give me a feedback about how window managers perform in hi-resolution monitors? Particularly, is 4K overkill? I also want to use ddcutil to change brightness (I have very sensitive eyes 😞 )<a href="https://mastodon.social/tags/arch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#arch</a> <a href="https://mastodon.social/tags/gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gentoo</a> <a href="https://mastodon.social/tags/debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debian</a>

Jérôme Carretero<a href="https://mastodon.social/@jk" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jk</a> It may be personal but I see it with a much different perspective.I'm *immensely grateful* that it's possible to have a machine with so many millions of SLOC running pretty much exactly how I want, respecting my freedom, with me contributing so little in return.I'm also grateful that I can get to learn and know what's inside, and via the stream of updates and breakages, essentially be getting free continuous learning and also staying updated.I'm purposely running <a href="https://mastodon.zougloub.eu/tags/gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gentoo</a> on my main machine, playing that Tamagotchi game very much. When I want to "get things done without surprises", I use a "stable" "supply chain", trading off my own risk against reduced functionality, increased cost.The good thing with "Linux" is that in no case you lose your freedom.

Anoncheg<a href="https://techhub.social/tags/dailyreport" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dailyreport</a> <a href="https://techhub.social/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> <a href="https://techhub.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://techhub.social/tags/gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gentoo</a> <a href="https://techhub.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://techhub.social/tags/compiler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compiler</a> <a href="https://techhub.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> I compiled Rust from sources with alternative compiler Mrustc (C++) without any binary blobs.As you may know Rust compiler distributed as Rust sources meant to be build by older "snapshot" of itself. Which violate open source paradigm.I was able to solve this in Gentoo GNU/Linux OS with reproducible way. First I compile Rust 1.74 version and then in chain I compile all versions to 1.84.All steps took approximately 8 hours, but after it is fast to compile new version, without blobs. 蠡

Oleh GordiOkay, now I'm so lazy that I'm writing a zsh script to automatically activate a `venv` if it's in the current directory and deactivate on any parent directories.// check code in first reply, change `TRUST_DIR` and `venv` if you prefer another name.<a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.social/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOS</a> <a href="https://mastodon.social/tags/gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gentoo</a> <a href="https://mastodon.social/tags/zsh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zsh</a> <a href="https://mastodon.social/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#python</a>

ShaiBuon compleanno, Gentoo! 🎉 🥳 Ecco la tua torta, vai avanti e compilatela da solo 😁 <a href="https://livellosegreto.it/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a> <a href="https://livellosegreto.it/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>

NerdNextDoor :Blobhaj:Nothing like trying to compile <a href="https://mastodon.social/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a> packages and <a href="https://mastodon.social/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows</a> Server 2003 using Windows 10 at the same time while listening to <a href="https://mastodon.social/tags/Lagtrain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Lagtrain</a>.It's kind of soothing watching it all come together.<a href="https://mastodon.social/tags/WindowsServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WindowsServer</a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/GentooLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GentooLinux</a> <a href="https://mastodon.social/tags/Music" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Music</a> <a href="https://mastodon.social/tags/Tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tech</a> <a href="https://mastodon.social/tags/Technology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Technology</a>

Dion Moult<a href="https://aus.social/@galoisghost" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@galoisghost</a> <a href="https://mastodon.social/tags/gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gentoo</a> :)

thesaigoneerThis week's Gang of Four consists of Slackware KDE 6.3.3, Gentoo with dwm & Qtile Wayland, AerynOS with Gnome 48 and Asterix Saigon, my Aurora beta spin (Fedora 42). Although all are rolling and rocking this absolutely feels solid 🪨💪🏻 <a href="https://fosstodon.org/tags/AerynOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AerynOS</a> <a href="https://fosstodon.org/tags/slackware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#slackware</a> <a href="https://fosstodon.org/tags/Aurora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Aurora</a> <a href="https://fosstodon.org/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a>

Steve<a href="https://mastodon.social/@itsfoss" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@itsfoss</a> <a href="https://mastodon.social/tags/gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gentoo</a> for me!

FurbyOnSteroidsIdk wtf I did, but whenever I update my <a href="https://ohai.social/tags/nixos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixos</a> it just compiles everything from source. I guess this is what it feels like to use <a href="https://ohai.social/tags/gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gentoo</a>. Update and don't do anything else because the update process takes 2 hours at close to 100% cpu usage <a href="https://ohai.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>

mgorny-nyan (he) :autism:🙀🚂🐧<a href="https://social.treehouse.systems/@mgorny/114137227235533135" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://social.treehouse.systems/@mgorny/114137227235533135</a>Yes, they did it. <a href="https://social.treehouse.systems/tags/setuptools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#setuptools</a> literally made lots of <a href="https://social.treehouse.systems/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> packages (such as requests) explode, apparently in order to resolve a problem with their own test suite. Sure, that stuff has been deprecated for a long time. But as I've said multiple times, *nobody* sees these deprecation warnings.Well, unless they run <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a>, because we have literally the only Python package installer out there that catches and repeats setuptools deprecation warnings verbosely. But we don't have time to fix deprecations in upstream packages while upstreams are making sure to set up fires all over the place, all the time.<a href="https://github.com/pypa/setuptools/issues/4910" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/pypa/setuptools/issues/4910</a><a href="https://social.treehouse.systems/tags/packaging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#packaging</a>

Jons MostovojsClimate change nightmare, tech edition: <a href="https://social.doma.dev/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> workflow using <a href="https://social.doma.dev/tags/Nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nix</a> on <a href="https://social.doma.dev/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a> to fine-tune a <a href="https://social.doma.dev/tags/JVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JVM</a> implementation of a <a href="https://social.doma.dev/tags/blockchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blockchain</a>-enabled <a href="https://social.doma.dev/tags/LLM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLM</a>.Thanks for inspiration, <a href="https://fosstodon.org/@faassen" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@faassen</a>!

RaniriI could be called as arrogant and gatekeeper, but if you have no experience with terminal, command line, terminal user interface, stay away from advance Distro. <a href="https://mastodon.social/tags/gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gentoo</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.social/tags/terminal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#terminal</a>

Giuseppe Ranieri 🚁 :verified:Gentoo rebooted. Mi sono messo a resuscitare l'ultimo mio desktop auto costruito. La vecchia scheda video una GT8600 MSI passiva era moribonda, da sempre forse, il che rendeva il pc instabile. Sostituita con una GT710 é rinato.Gentoo reinstallata e visto che avevo fatto le cose a modo ho rimontato le sue partizioni boot e home.XFS on the rock.I suoi 17 anni se li porta bene!Batteria CMOS sostituita!<a href="https://mastodon.uno/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a> <a href="https://mastodon.uno/tags/RetroLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RetroLinux</a> <a href="https://mastodon.uno/tags/backup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backup</a>

Recent searches

Search options

Administered by:

Server stats:

#gentoo