Search
1000 results for “Gentoo_eV”
-
It's been a while since I've complained about #RustLang itself, so…
Cargo insists on interacting with #git repositories. At the same time, cargo insists on vendoring an old version of #LibGit2 (1.6.2 FWICS). So, if your system is using a new git version (2.44.0), you won't be able to `cargo build`:
```
error: failed to determine package fingerprint for build script for uv v0.1.38 (/tmp/uv/crates/uv)Caused by:
failed to determine the most recently modified file in /tmp/uv/crates/uvCaused by:
failed to determine list of files in /tmp/uv/crates/uvCaused by:
failed to open git index at /tmp/uv/.git/Caused by:
invalid data in index - calculated checksum does not match expected; class=Index (10)
```You have to clone everything with `-c index.skipHash=false` to work around this.
But yeah, I'm sure there's a great benefit to using an outdated vendored C library that NIHs git.
-
Essentially, distro developers are firefighters, putting out fires made by careless upstreams.
What I've wasted time on, today:
- making the non-standalone test suite of #Hatchling (sigh) work without #UV again, so that a critical build dependency of a growing number of #Python packages could be tested everywhere
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cc6e54e1df5e0802198c793f39107a9028b8698f
https://bugs.gentoo.org/930662- fixing effectively dead (but with a promise of revival) #PassLib not to break random stuff via printing warnings when using newer #BCrypt versions
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c1e015b65b74283a51893672739c5e4784b95273
https://bugs.gentoo.org/925289- hacking the test suite of #ImageIO work using an offline copy of test data, rather than cloning its git repository at the beginning of tests
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=77ff4bc09d68067f2c635d43d446f308990e0873
I really wish people would consider donating to distro developers more often, rather than to projects that create this thankless work for us.
-
I tried #Box64 on my #MNTReform with #BananaPiCM4 yesterday. It's surprising how fast it is. #LoopHero and #WorldOfGoo are running pretty well, for instance.
I also tried #Parkitect and #ValhallaHills, but those weren't really playable. Valhalla Hills only rendered its UI, everything else was black (probably needs OpenGL features missing in #Panfrost), and #Parkitect crashed frequently.
Now I wonder if #Gentoo #Crossdev can be used for building/running #Box86?
-
I tried #Box64 on my #MNTReform with #BananaPiCM4 yesterday. It's surprising how fast it is. #LoopHero and #WorldOfGoo are running pretty well, for instance.
I also tried #Parkitect and #ValhallaHills, but those weren't really playable. Valhalla Hills only rendered its UI, everything else was black (probably needs OpenGL features missing in #Panfrost), and #Parkitect crashed frequently.
Now I wonder if #Gentoo #Crossdev can be used for building/running #Box86?
-
I tried #Box64 on my #MNTReform with #BananaPiCM4 yesterday. It's surprising how fast it is. #LoopHero and #WorldOfGoo are running pretty well, for instance.
I also tried #Parkitect and #ValhallaHills, but those weren't really playable. Valhalla Hills only rendered its UI, everything else was black (probably needs OpenGL features missing in #Panfrost), and #Parkitect crashed frequently.
Now I wonder if #Gentoo #Crossdev can be used for building/running #Box86?
-
I tried #Box64 on my #MNTReform with #BananaPiCM4 yesterday. It's surprising how fast it is. #LoopHero and #WorldOfGoo are running pretty well, for instance.
I also tried #Parkitect and #ValhallaHills, but those weren't really playable. Valhalla Hills only rendered its UI, everything else was black (probably needs OpenGL features missing in #Panfrost), and #Parkitect crashed frequently.
Now I wonder if #Gentoo #Crossdev can be used for building/running #Box86?
-
Let's reminisce on #LibAV, the #FFmpeg fork. I won't get into the details why it was forked because I've heard multiple versions and I'm biased.
During its primetime, LibAV was facing three difficulties. Firstly, FFmpeg held "the brand" — it defined what the users expected, it received the bulk of the donations and the contributions. Secondly, LibAV aimed to improve the code quality. This roughly meant that FFmpeg could easily merge improvements back (and they did) but not everything was fit to be merged the other way around. Thirdly, LibAV tried hard to clean stuff up and deprecate old API, effectively facing more backwards compatibility issues.
In the end, LibAV-related work would involve both keeping feature parity with FFmpeg, and patching software to support its API. Sometimes this meant dead software, for which you'd have to maintain patchsets forever. Sometimes it meant hostile upstreams, which involved maintaining and rebasing patchsets forever. Perhaps the most prominent example was the #mpv media player, that would first give LibAV a push by removing FFmpeg support and requiring LibAV, and then change their mind and remove LibAV support.
On top of that, the two library sets weren't ABI-compatible, so it was all-or-nothing. #Gentoo users would have to randomly rebuild all packages when a newly selected package or a version bump forced a switch. Binary distros have had it even worst. Debian eventually switched back to FFmpeg in 2015, Gentoo removed it in 2020, and LibAV itself was discontinued in 2022.
What brought this about? The news of corporate takeover of nginx, followed by its fork to FreeNginx. Not the first such a case, and certainly not the last — perhaps it's another variant of enshittification. OpenOffice was successfully forked into LibreOffice. BerkeleyDB is being phased out after its takeover by Oracle. LibreSSL is still alive alongside OpenSSL, thought it's not supported widely.
-
Let's reminisce on #LibAV, the #FFmpeg fork. I won't get into the details why it was forked because I've heard multiple versions and I'm biased.
During its primetime, LibAV was facing three difficulties. Firstly, FFmpeg held "the brand" — it defined what the users expected, it received the bulk of the donations and the contributions. Secondly, LibAV aimed to improve the code quality. This roughly meant that FFmpeg could easily merge improvements back (and they did) but not everything was fit to be merged the other way around. Thirdly, LibAV tried hard to clean stuff up and deprecate old API, effectively facing more backwards compatibility issues.
In the end, LibAV-related work would involve both keeping feature parity with FFmpeg, and patching software to support its API. Sometimes this meant dead software, for which you'd have to maintain patchsets forever. Sometimes it meant hostile upstreams, which involved maintaining and rebasing patchsets forever. Perhaps the most prominent example was the #mpv media player, that would first give LibAV a push by removing FFmpeg support and requiring LibAV, and then change their mind and remove LibAV support.
On top of that, the two library sets weren't ABI-compatible, so it was all-or-nothing. #Gentoo users would have to randomly rebuild all packages when a newly selected package or a version bump forced a switch. Binary distros have had it even worst. Debian eventually switched back to FFmpeg in 2015, Gentoo removed it in 2020, and LibAV itself was discontinued in 2022.
What brought this about? The news of corporate takeover of nginx, followed by its fork to FreeNginx. Not the first such a case, and certainly not the last — perhaps it's another variant of enshittification. OpenOffice was successfully forked into LibreOffice. BerkeleyDB is being phased out after its takeover by Oracle. LibreSSL is still alive alongside OpenSSL, thought it's not supported widely.
-
Let's reminisce on #LibAV, the #FFmpeg fork. I won't get into the details why it was forked because I've heard multiple versions and I'm biased.
During its primetime, LibAV was facing three difficulties. Firstly, FFmpeg held "the brand" — it defined what the users expected, it received the bulk of the donations and the contributions. Secondly, LibAV aimed to improve the code quality. This roughly meant that FFmpeg could easily merge improvements back (and they did) but not everything was fit to be merged the other way around. Thirdly, LibAV tried hard to clean stuff up and deprecate old API, effectively facing more backwards compatibility issues.
In the end, LibAV-related work would involve both keeping feature parity with FFmpeg, and patching software to support its API. Sometimes this meant dead software, for which you'd have to maintain patchsets forever. Sometimes it meant hostile upstreams, which involved maintaining and rebasing patchsets forever. Perhaps the most prominent example was the #mpv media player, that would first give LibAV a push by removing FFmpeg support and requiring LibAV, and then change their mind and remove LibAV support.
On top of that, the two library sets weren't ABI-compatible, so it was all-or-nothing. #Gentoo users would have to randomly rebuild all packages when a newly selected package or a version bump forced a switch. Binary distros have had it even worst. Debian eventually switched back to FFmpeg in 2015, Gentoo removed it in 2020, and LibAV itself was discontinued in 2022.
What brought this about? The news of corporate takeover of nginx, followed by its fork to FreeNginx. Not the first such a case, and certainly not the last — perhaps it's another variant of enshittification. OpenOffice was successfully forked into LibreOffice. BerkeleyDB is being phased out after its takeover by Oracle. LibreSSL is still alive alongside OpenSSL, thought it's not supported widely.
-
Let's reminisce on #LibAV, the #FFmpeg fork. I won't get into the details why it was forked because I've heard multiple versions and I'm biased.
During its primetime, LibAV was facing three difficulties. Firstly, FFmpeg held "the brand" — it defined what the users expected, it received the bulk of the donations and the contributions. Secondly, LibAV aimed to improve the code quality. This roughly meant that FFmpeg could easily merge improvements back (and they did) but not everything was fit to be merged the other way around. Thirdly, LibAV tried hard to clean stuff up and deprecate old API, effectively facing more backwards compatibility issues.
In the end, LibAV-related work would involve both keeping feature parity with FFmpeg, and patching software to support its API. Sometimes this meant dead software, for which you'd have to maintain patchsets forever. Sometimes it meant hostile upstreams, which involved maintaining and rebasing patchsets forever. Perhaps the most prominent example was the #mpv media player, that would first give LibAV a push by removing FFmpeg support and requiring LibAV, and then change their mind and remove LibAV support.
On top of that, the two library sets weren't ABI-compatible, so it was all-or-nothing. #Gentoo users would have to randomly rebuild all packages when a newly selected package or a version bump forced a switch. Binary distros have had it even worst. Debian eventually switched back to FFmpeg in 2015, Gentoo removed it in 2020, and LibAV itself was discontinued in 2022.
What brought this about? The news of corporate takeover of nginx, followed by its fork to FreeNginx. Not the first such a case, and certainly not the last — perhaps it's another variant of enshittification. OpenOffice was successfully forked into LibreOffice. BerkeleyDB is being phased out after its takeover by Oracle. LibreSSL is still alive alongside OpenSSL, thought it's not supported widely.
-
After an update, when the output of #NeedReboot includes all the browsers, the sound system, X, the window manager, all the daemons, and even emacs, that is a good time to reboot into #SystemRescue and fsck the disks. (Related: can't wait for #SpinRite 6.1)
#PreviousUpTime: 17 days, 16 hours
#CurrentUpTime: 12 minutes. -
Wow. I find this scrying back to 26 May 2021
I scry, with my little eye..
Enjoy the stroll down memory lane, but a dark day it was
___
Freenode Commits Suicide - Evacuations Underway - Breaking News!
[**PLEASE BOOST**]
A few hours ago, under the direct intervention of the Crown Prince Andrew Lee of South Korea, beginning with about 700 IRC channells, Freenode staff began hijacking and purgings all channels that had mention of "Libera" in their channel topic.
https://www.devever.net/~hl/freenode_abuse2
More details in a minute, but first, just a short list of the sort of channels that have been seized by Mr. Lee in what can only be described a suicidal and vindictive usurpation of some of the most prominent names in the world of computer software:
#wikipedia
#intel
#python
#ubuntu
#rust
##linux
#openbsd
# fosdem
#clearlinux
The Gentoo channels, Haskel, Weechat, etc., etc., ad nauseum...
Basically, the pillars of the software world, Linux, C, major Fortune 500 companies - you name it. POOF!
Earlier articles on the subjects of what has been widely characterized and regarded as a hostile takeover of freenode in the Media were published here over the course of the past few days and fortunately, our registered projects with freenode and Libera were previously announced as having been secured as well.
Only one of our channels has been affected, because the second wave of hijacking was administered by what we can only presume to be a misbehaving, poorly configured bot, in that it seized ownership of channels that merely had mentions of the string "Libera" or "Libera.Chat" by anyone in the channels.
We received the following **Apology** from Andrew Lee with this statement, at 21:15:30hrs PST, posted directly in one of our channels affected by this second wave of hijackings:
<snip>
-rasengan- [Global Notice] In the recent policy enforcement, some channels were erroneously included. We greatly apologize for the inconvenience. Please contact us in #freenode-services or [email protected]. Thanks for your patience and choosing freenode!
</snip>
To that we say, Fuck you freenode, and Fuck you very much Andrew Lee - go eat a fucking dick you punk ass bitch!
By tomorrow, the usual news media outlets will have published freenode's Obituary.
I'm going to post more discussion links to follow below, but suffice it to say that the Earth is indeed flat for freenode, and that ship has sailed over the edge into the abyss.
In the meantime, we urge everyone who has long standing friendships and associations with others still there to find them, and let them know where you'll be following the vacuum left after this implosion.
R.I.P. freenode
https://mastodon.sdf.org/@kline/106299403921451814
https://pleroma.envs.net/notice/A7d3VZuH1myJ6gJS2C
<snip>
comparison of channels that have had their topics forcibly changed to reflect that they remain the official channels for registered projects (Libera string removed from topics):
https://archive.is/uHw1g
https://netsplit.de/channels/?net=freenode&chat=libera&num=100
</snip>
https://www.teddit.net/r/haskell/comments/nl74hc/freenode_has_unilaterally_taken_over_haskell/
https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=freenode&sort=byDate&type=story
Twatter is litterally on fire, it's such a mess that I just selected some random post that embodies the type of activities going on there:
https://nitter.fdn.fr/Slatzism/status/1397468106918928386
It's total and complete fuckery.
#tallship #Vger #freenode #libera #irc #FOSS #andrew_lee #fuckery
⛵
.
2021-05-26 01.14.55 twitter.com… -
I just minted my first NFT. I made some initial mistakes on the first try, but I eventually got it resolved. Anyways, there 25/25 mints available. Grab them while you can.
"Sleepy Gentoo" - ACEO art card collectible https://rarible.com/token/0xd07dc4262bcdbf85190c01c996b4c06a461d2430:700697? #rarible #ethereum #nft via @[email protected]
-
@aral
Be careful! That's how it starts.I switched from OS X to Pop!_OS, but that was just the beginning. Pretty soon, I'd made my way on to #arch. These days, I'm running a lot of #suckless tools, including #dwm, #dmenu, and #st—and I don't even *have* a display manager. Now, heaven help me, I'm even considering installing #gentoo or #void.
-
So I have a technology artifact from #1999. A #maxtor Diamondpoint #pata #ide hard drive. I've used it on and off between 1999 and 2020 (when I retired it). The #SMART #power_on_hours for this thing are: 137478! That's 15.69 years of up time on that drive. :) It's run everything from old RedHat (not RHEL), Windows Millennium, Fedora, Gentoo, Debian and Ubuntu. And it's still works. It has that old fashioned whine... This thing is a juggernaut!
-
So I have a technology artifact from #1999. A #maxtor Diamondpoint #pata #ide hard drive. I've used it on and off between 1999 and 2020 (when I retired it). The #SMART #power_on_hours for this thing are: 137478! That's 15.69 years of up time on that drive. :) It's run everything from old RedHat (not RHEL), Windows Millennium, Fedora, Gentoo, Debian and Ubuntu. And it's still works. It has that old fashioned whine... This thing is a juggernaut!
-
So I have a technology artifact from #1999. A #maxtor Diamondpoint #pata #ide hard drive. I've used it on and off between 1999 and 2020 (when I retired it). The #SMART #power_on_hours for this thing are: 137478! That's 15.69 years of up time on that drive. :) It's run everything from old RedHat (not RHEL), Windows Millennium, Fedora, Gentoo, Debian and Ubuntu. And it's still works. It has that old fashioned whine... This thing is a juggernaut!
-
Alright new instance new #introduction time. I should really just copy this somewhere so I don't have to keep retyping it, given how much I move.
I'm #queer, and #polyamorous who's about 30 years old at the time of writing. I do tend to hop around fediverse instances, but I'd like to stop that at some point. I liked Friendica a lot, but my last 2 instances died very suddenly, and I decided against trying a third time. My more stationary account is @[email protected], which should be up indefinitely if I don't decide to stop giving omg.lol my money (unlikely, they deserve it!)
I'm a #gamer, and have been for as long as I can remember. I play #FinalFantasyXIV, #GuildWars2, and #WurmOnline for #MMORPG, and I rotate between a few different non MMOs. I tend to play a lot of #VisualNovel, #Mahjong on Riichi City (and hopefully some on FFXIV once cross-DC queues hit NA!), and a lot of #NSFW games. If you have any suggestions on those don't hesitate to DM me, I'm always looking for more!
For some technical hobbies, I'm into #3DPrinting, and I've dabbled in #Soldering to make my own #MechanicalKeyboard. Didn't design it, but I did put it together without a kit :D
Generally I'm very into #FOSS, and #HomeLab. I've also been a #Linux user since 2010. Over the years I've used several flavors of Ubuntu, Debian, EndeavourOS, Garuda Linux, Arch Linux, and currently a #Gentoo user. Also #Emacs is the best piece of software to ever be released.
I'm a #Writer, though I'm currently being very slow writing this novella. Hoping to turn it into a VN, but I can't draw to save my life, and it's real expensive to commission that many images. Might just do a light novel-style thing and throw an image in with each chapter.
For crafts I like #Knitting, and I can #Crochet though do that very infrequently because it hurts. I also do #TabletWeaving, though I'm fairly new at that.
That's just about everything! I do occasionally boost porn, and will probably post my own at some point. Images will be CW'd, text likely will not be, as it causes some distress figuring out what to CW -
I tried a bit more Linux distro investigation, and I think I just should have listened to @hipsterelectron in the first place.
TL;DR: If you want to run Linux without systemd, with something other than GNOME as a desktop (which is implied if you don't want systemd), and if you're comfortable with using the command line for installation, Alpine Linux is a great choice. The default install has zero systemd.
Yes, it's a command-line install, but it's far easier to install than Gentoo. The core OS install was so fast that I thought it had failed. Once I had that sorted and had installed a few support items, the setup-desktop script installed the whole of KDE and Wayland in a couple of minutes. I rebooted and everything worked. It even got the high DPI screen's resolution right for both KDE and sddm, which literally no other distro I've tried has managed.
A lack of bloat doesn't just make Alpine good for containers, it's also really responsive in general use. (Which is how computers ought to be with modern hardware.)
The package manager is nice. Think APT, but much faster. It automatically keeps a separate record of what you've actually asked to install versus dependencies that were dragged in, for easy automatic bloat removal.
Downsides:
- No proprietary Nvidia driver available, you need to use nouveau, so no CUDA or high performance gaming.
- Documentation (including installation) is scattered in pieces on a wiki.
- A lot less stuff prepackaged for you than Debian. Check https://pkgs.alpinelinux.org/ to see if things you need are available.
- You'll need to get used to some things being different thanks to use of busybox, no sudo, no bash by default, and so on.My conclusion: Command line user? Try Alpine. Everyone else? Use Debian, and hope they move away from systemd.
I might revise this opinion if things break a lot during regular updates (hello Fedora), time will tell. #AlpineLinux #Linux
-
I tried a bit more Linux distro investigation, and I think I just should have listened to @hipsterelectron in the first place.
TL;DR: If you want to run Linux without systemd, with something other than GNOME as a desktop (which is implied if you don't want systemd), and if you're comfortable with using the command line for installation, Alpine Linux is a great choice. The default install has zero systemd.
Yes, it's a command-line install, but it's far easier to install than Gentoo. The core OS install was so fast that I thought it had failed. Once I had that sorted and had installed a few support items, the setup-desktop script installed the whole of KDE and Wayland in a couple of minutes. I rebooted and everything worked. It even got the high DPI screen's resolution right for both KDE and sddm, which literally no other distro I've tried has managed.
A lack of bloat doesn't just make Alpine good for containers, it's also really responsive in general use. (Which is how computers ought to be with modern hardware.)
The package manager is nice. Think APT, but much faster. It automatically keeps a separate record of what you've actually asked to install versus dependencies that were dragged in, for easy automatic bloat removal.
Downsides:
- No proprietary Nvidia driver available, you need to use nouveau, so no CUDA or high performance gaming.
- Documentation (including installation) is scattered in pieces on a wiki.
- A lot less stuff prepackaged for you than Debian. Check https://pkgs.alpinelinux.org/ to see if things you need are available.
- You'll need to get used to some things being different thanks to use of busybox, no sudo, no bash by default, and so on.My conclusion: Command line user? Try Alpine. Everyone else? Use Debian, and hope they move away from systemd.
I might revise this opinion if things break a lot during regular updates (hello Fedora), time will tell. #AlpineLinux #Linux
-
I tried a bit more Linux distro investigation, and I think I just should have listened to @hipsterelectron in the first place.
TL;DR: If you want to run Linux without systemd, with something other than GNOME as a desktop (which is implied if you don't want systemd), and if you're comfortable with using the command line for installation, Alpine Linux is a great choice. The default install has zero systemd.
Yes, it's a command-line install, but it's far easier to install than Gentoo. The core OS install was so fast that I thought it had failed. Once I had that sorted and had installed a few support items, the setup-desktop script installed the whole of KDE and Wayland in a couple of minutes. I rebooted and everything worked. It even got the high DPI screen's resolution right for both KDE and sddm, which literally no other distro I've tried has managed.
A lack of bloat doesn't just make Alpine good for containers, it's also really responsive in general use. (Which is how computers ought to be with modern hardware.)
The package manager is nice. Think APT, but much faster. It automatically keeps a separate record of what you've actually asked to install versus dependencies that were dragged in, for easy automatic bloat removal.
Downsides:
- No proprietary Nvidia driver available, you need to use nouveau, so no CUDA or high performance gaming.
- Documentation (including installation) is scattered in pieces on a wiki.
- A lot less stuff prepackaged for you than Debian. Check https://pkgs.alpinelinux.org/ to see if things you need are available.
- You'll need to get used to some things being different thanks to use of busybox, no sudo, no bash by default, and so on.My conclusion: Command line user? Try Alpine. Everyone else? Use Debian, and hope they move away from systemd.
I might revise this opinion if things break a lot during regular updates (hello Fedora), time will tell. #AlpineLinux #Linux
-
I tried a bit more Linux distro investigation, and I think I just should have listened to @hipsterelectron in the first place.
TL;DR: If you want to run Linux without systemd, with something other than GNOME as a desktop (which is implied if you don't want systemd), and if you're comfortable with using the command line for installation, Alpine Linux is a great choice. The default install has zero systemd.
Yes, it's a command-line install, but it's far easier to install than Gentoo. The core OS install was so fast that I thought it had failed. Once I had that sorted and had installed a few support items, the setup-desktop script installed the whole of KDE and Wayland in a couple of minutes. I rebooted and everything worked. It even got the high DPI screen's resolution right for both KDE and sddm, which literally no other distro I've tried has managed.
A lack of bloat doesn't just make Alpine good for containers, it's also really responsive in general use. (Which is how computers ought to be with modern hardware.)
The package manager is nice. Think APT, but much faster. It automatically keeps a separate record of what you've actually asked to install versus dependencies that were dragged in, for easy automatic bloat removal.
Downsides:
- No proprietary Nvidia driver available, you need to use nouveau, so no CUDA or high performance gaming.
- Documentation (including installation) is scattered in pieces on a wiki.
- A lot less stuff prepackaged for you than Debian. Check https://pkgs.alpinelinux.org/ to see if things you need are available.
- You'll need to get used to some things being different thanks to use of busybox, no sudo, no bash by default, and so on.My conclusion: Command line user? Try Alpine. Everyone else? Use Debian, and hope they move away from systemd.
I might revise this opinion if things break a lot during regular updates (hello Fedora), time will tell. #AlpineLinux #Linux
-
I tried a bit more Linux distro investigation, and I think I just should have listened to @hipsterelectron in the first place.
TL;DR: If you want to run Linux without systemd, with something other than GNOME as a desktop (which is implied if you don't want systemd), and if you're comfortable with using the command line for installation, Alpine Linux is a great choice. The default install has zero systemd.
Yes, it's a command-line install, but it's far easier to install than Gentoo. The core OS install was so fast that I thought it had failed. Once I had that sorted and had installed a few support items, the setup-desktop script installed the whole of KDE and Wayland in a couple of minutes. I rebooted and everything worked. It even got the high DPI screen's resolution right for both KDE and sddm, which literally no other distro I've tried has managed.
A lack of bloat doesn't just make Alpine good for containers, it's also really responsive in general use. (Which is how computers ought to be with modern hardware.)
The package manager is nice. Think APT, but much faster. It automatically keeps a separate record of what you've actually asked to install versus dependencies that were dragged in, for easy automatic bloat removal.
Downsides:
- No proprietary Nvidia driver available, you need to use nouveau, so no CUDA or high performance gaming.
- Documentation (including installation) is scattered in pieces on a wiki.
- A lot less stuff prepackaged for you than Debian. Check https://pkgs.alpinelinux.org/ to see if things you need are available.
- You'll need to get used to some things being different thanks to use of busybox, no sudo, no bash by default, and so on.My conclusion: Command line user? Try Alpine. Everyone else? Use Debian, and hope they move away from systemd.
I might revise this opinion if things break a lot during regular updates (hello Fedora), time will tell. #AlpineLinux #Linux
-
@rl_dane @msdropbear42 @MsDropbear42
Hey R.L. Dane,
as per your OP in this thread, I've been using #Remmina for years. X2Go, RDP, WhatEv really floats yer boat ⛵ , it's there.
Uh, oh, I feel a tangent coming on... Okay not to hijack your thread, but maybe you can offer a bit of your perspective on flatpak vs appimage alternatives, since I don't prefer either, and usually will go out of my way to create a native package for WhatEv distro I'm using if it doesn't exist, or just compile from source rawdawg if need be like I did with #Zed (which only impresses me because of Git integration and Vim bindings; and it's Rust) - Jury's still out on that one though.
Anyway, I just broke down and installed a flatpak for the #LaGrange browser because I got a bit lazy and didn't wanna make the .deb for myself.
Okay, back to your situation...
Remmina HERE is pretty comprehensive with the native package managers with ready to go .deb's for #Forky & Sid, #SlackBuild for #Slackware, #FreeBSD & #OpenBSD ports, #Devuan, #Gentoo, #Guix, and #Kali just to name some.
It's pretty straight-forward and a single package to accommodate a plethora of methodologies so you can use it as your Varsity first string go-to in a pinch most of the time.
Even better, is the fact that they don't have an ewb00ntew maintainer, lolz... Coz frinds don't let frinds run ewb00tew :p
-
@rl_dane @msdropbear42 @MsDropbear42
Hey R.L. Dane,
as per your OP in this thread, I've been using #Remmina for years. X2Go, RDP, WhatEv really floats yer boat ⛵ , it's there.
Uh, oh, I feel a tangent coming on... Okay not to hijack your thread, but maybe you can offer a bit of your perspective on flatpak vs appimage alternatives, since I don't prefer either, and usually will go out of my way to create a native package for WhatEv distro I'm using if it doesn't exist, or just compile from source rawdawg if need be like I did with #Zed (which only impresses me because of Git integration and Vim bindings; and it's Rust) - Jury's still out on that one though.
Anyway, I just broke down and installed a flatpak for the #LaGrange browser because I got a bit lazy and didn't wanna make the .deb for myself.
Okay, back to your situation...
Remmina HERE is pretty comprehensive with the native package managers with ready to go .deb's for #Forky & Sid, #SlackBuild for #Slackware, #FreeBSD & #OpenBSD ports, #Devuan, #Gentoo, #Guix, and #Kali just to name some.
It's pretty straight-forward and a single package to accommodate a plethora of methodologies so you can use it as your Varsity first string go-to in a pinch most of the time.
Even better, is the fact that they don't have an ewb00ntew maintainer, lolz... Coz frinds don't let frinds run ewb00tew :p
-
@rl_dane @msdropbear42 @MsDropbear42
Hey R.L. Dane,
as per your OP in this thread, I've been using #Remmina for years. X2Go, RDP, WhatEv really floats yer boat ⛵ , it's there.
Uh, oh, I feel a tangent coming on... Okay not to hijack your thread, but maybe you can offer a bit of your perspective on flatpak vs appimage alternatives, since I don't prefer either, and usually will go out of my way to create a native package for WhatEv distro I'm using if it doesn't exist, or just compile from source rawdawg if need be like I did with #Zed (which only impresses me because of Git integration and Vim bindings; and it's Rust) - Jury's still out on that one though.
Anyway, I just broke down and installed a flatpak for the #LaGrange browser because I got a bit lazy and didn't wanna make the .deb for myself.
Okay, back to your situation...
Remmina HERE is pretty comprehensive with the native package managers with ready to go .deb's for #Forky & Sid, #SlackBuild for #Slackware, #FreeBSD & #OpenBSD ports, #Devuan, #Gentoo, #Guix, and #Kali just to name some.
It's pretty straight-forward and a single package to accommodate a plethora of methodologies so you can use it as your Varsity first string go-to in a pinch most of the time.
Even better, is the fact that they don't have an ewb00ntew maintainer, lolz... Coz frinds don't let frinds run ewb00tew :p
-
Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.
So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.
Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.
So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".
-
“X is dead, Wayland is the future! XLibre is DOA.” they said. But who would believe in this? Not our community. They freed one screen after another and call this #liberatedscreens. Now here too. Not every Friday, but on Fridays. This time: XLibre on Gentoo, daily since the beginning. https://github.com/orgs/X11Libre/discussions/211 #xlibre
-
#HDF5 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 #CMake 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 #Arch, #Conda-forge, #Debian, #Fedora, #Gentoo) 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. -
I suppose I could use my experience to give some #PEP517 build system recommendations.
For pure #Python packages:
1. #flit_core (https://pypi.org/project/flit-core/) — it's lightweight and simple, and has no dependencies (in modern Python versions, for older Pythons it vendors tomli).
2. #hatchling (https://pypi.org/project/hatchling/) — it's popular and quite powerful, but has many vendored dependencies and no stand-alone test suite (which makes it painful to maintain in #Gentoo).
For Python packages with C extensions: #meson-python (https://pypi.org/project/meson-python/) — which combines the power and correctness of meson build system with good very Python integration.
For Python packages with Rust extensions: #maturin (https://pypi.org/project/maturin/) — which is simply a good builder for precisely that kind of packages.
Now, I strongly discourage:
A. #setuptools — lots of vendored NIH dependencies (that can alternatively be unvendored for cyclic deps), lots of deprecations over time (we're still seeing tons of deprecation warnings all over the place), many unsolved bugs (e.g. parallel C extension builds are broken in a few ways), a lot of technical debt, and if all that wasn't enough, it's slow.
B. #poetry-core — a very tricky build system with lots of pitfalls (I've reported a lot of mistakes done when migrating to it).
C. Practically any other build system — writing new backends is trivial, so everyone and their grandmother must have one. And then, they often carry a lot of NIH dependencies (if you're reinventing a build system, you may reinvent everything else), lack experience and reintroduce the same bugs. And if that wasn't enough, packaging them in distributions is a lot of work for no real benefit to anyone.