![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
I really like emerge/portage, even w/out the “candy” feature enabled. Great color highlighting, and verbose messages about any config change(s) needed.
An eclectic #nerdy #weirdo.
In addition to tech, #Linux, and other things #FLOSS, I’m also into #travel, jam bands (mostly Grateful Dead), music festivals, and anything related to exploring the #cosmos.
All puns are intended.
#actuallyautistic #deadhead #hockey
I really like emerge/portage, even w/out the “candy” feature enabled. Great color highlighting, and verbose messages about any config change(s) needed.
“Stable” doesn’t necessarily refer to “reliable,” depending on the context. Stable is often used in reference to how often a distro releases new versions of the applications. Using Audacity as an example, in the current release of the distro, they’ll release security & bug fixes for version 2, but if you want version 3, you’ll have to wait until the next distro release.
Upgrades to a new version of an application can introduce new ways of using the app (i.e. icons in different places, how user-created files are written to disk, etc.), which is disruptive to enterprise op’s, which is why Debian & RHEL take this approach.
Hopefully that helps clarify things.
I definitely prefer it over Snaps or appimages. Straight-forward to update, and Flatseal provides a nice GUI to control permissions (if needed). Themes may not work properly, but whatever, not a big deal for me.
The distro’s repo is always my go-to. If it’s not available there, then flatpak, and I’ll use appimage under duress. If that doesn’t work, I’ll figure out a different solution.
I say go for it. I’ve been using it for about 2 years, and I no longer feel like distro-hopping (not sure if you fall into that category of Linux user), because it’s not opinionated about how it’s meant to be used. It gives you all the tools (and foot-guns) to do whatever you want with your computer.
You don’t need separate computers for a local mirror and/or build server to run Gentoo, I’ve never done that. I’ve never owned a Mac, so I can’t really offer any tips hardware-wise, but use a live USB of a distro that you’re already familiar with, so you can refer to the handbook as you go. The people on Gentoo’s IRC channel & forums are very helpful if you come against any roadblocks.
It does take a while, not gonna gloss over that. Once you have it installed, there are very few issues that would require a full re-install. Portage is an awesome package manager, the language of its warnings/errors took some time to wrap my brain around, but it’s very verbose in describing what’s going on.
I really like the simple design that separates the results into docs/blogs/magazines. Obviously, the results reflect the current state, but I appreciate your approach in both the design & sourcing the search results. I think there’s a lot of potential for this to be a regular part of my toolbox, hopefully this takes off!
Yeah, I totally get that, I have really bad memories myself.
If it’s an ncurses/similar interface that enables keyboard navigation through dmesg/journalctl, and provides info that allows us to properly diagnose it, I can see this being useful.
But yeah, I’ll admit that simply saying “BSOD’s are coming to Linux” without additional info about the implementation does bring feelings of dread in me.
…and of course, this news is getting mixed reactions from the Linux nerds…
Back when I used Windows, I remember the BSOD’s being about as useful to me as someone pointing in opposite directions saying “he/she/they went that way.” So long as the new Linux blue screens provide info that’s actually useful in diagnosing the problem(s), I see no issues with this. [shrugs]
I second raptir’s note about running zypper dup in the terminal to do system updates. Zypper’s a bit slow because it lacks parallel downloads, but it provides good info if there are any issues.
If you plan to use flatpaks, add the flathub repo with the --user option, and use that one to install. If I didn’t go that route, it prompted me to enter my password for every flatpak app with an update. I’m also a deplorable Plasma user 😜, I don’t know if the same behavior happens with Gnome software, it may be a weird Discover thing (shrugs).
Also, if you need the non-free multimedia codecs, run the following commands:
zypper install opi
opi codecs
Automates adding the Packman repo & switching the relevant packages.
Those are the main quirks I learned with Tumbleweed.
Looking forward to see how this version performs, keep up the great work!
[crosses fingers for a smooth transition]
Hope you & your family are recovering well, I had COVID last summer, and I was out of commission for a little over a week.
Focus on getting healthy, listen to your body, and don’t rush back to the studio.
There are three other seasons if we get bored. ;-)
I never recommend Manjaro, even for experienced users. Multiple times, they’ve let their ssl certificats expire, and renewing those has been easy to automate for a number of years at this point. There have been a number of cases where they ship work-in-progress versions of software as part of their default install, and there was an open letter posted calling this out: https://dont-ship.it
So in my opinion, Manjaro leaves much to be desired from a project governance standpoint.
Now, using an Arch-based distro that does the install process for you doesn’t absolve you from learning what it takes to maintain an Arch install; at some point, something will crop-up that requires manual intervention to get back up & running again after an update.
If that is what you’re looking for, I suggest EndeavourOS.
If you want a rolling release, I suggest going with openSUSE Tumbleweed. The installer allows you to pick & choose what you do/don’t want/need, and has a great rollback system in case an update causes problems.
Otherwise, I would suggest Fedora. Stays very current, and the in-place upgrade process is very seamless at this point.
Can’t say that I’ve really used any of the features mentioned in this list, so doesn’t really affect my experience negatively. Also, updating some icon sets to fit with the overall theme would provide a more unified experience. So two thumbs-up from me for removing code that, by & large, wasn’t getting used, should help maintaining it in the long run.
I totally get why this is being put forth. Watch Brodie’s videos on the Wayland portals (after binging on LUS, of course ;-) ), and notice which DE is more actively helpful in making the portals better…I guarantee you it doesn’t start with a “G.” They actually mention this in the change proposal, and I doubt that Red Hat is blind to this difference.
It’ll be interesting to see how this plays-out.