I guess now that gdm, gnome-shell, & gnome-session have been updated for 51 I should start updating gnome slackbuilds....
I'm always waiting for the day where it just doesn't work anymore, but that day never comes. 🤣
Remote
jloc0
@jloc0@mastodon.sdf.org
mastodon 4.7.3Hi, my name is Jay, but the internet has always called me r0ni. I’m from the golden age of the web and I still pretend I live there. In a former life I covered emulation news (late 90s), then I withdrew from Web 2.0 and continued to love the great things from then. Slackware & console emulation are my the things that keep me up at night. I live in a home with 2 dogs & a cat, my son (the only one left of 4), and my SO. Waiting for the end of the world.
198 Followers
208 Following
50 Posts
Joined August 28, 2024
Previous Mastodon Acct. (post history):
MAME MacOS:
Slackware Repositories:
Archaic Ruins (time capsule):
#Hyprland 0.55.0 is now available within the #slackaroni repository along with various rebuilds following an update for the required #hyprutils as well. Cheers!
I'll push arm64 packages soon for the minority of people not only using #slackware but #slackwareaarch64 and using my repos (this has to be like 3 people ;)
Have yall seen the names #bluefin gives to things? I need to step up my naming game.
🤣
I've uploaded #libreoffice 26.2.3 & #firefox 150.0.1 along with some #hyprwm updates and rebuilds to match for a download heavy update to #slackaroniaarch64 today.
Ok, I'll be uploading the #ktown aarch64 updates shortly, but in the meantime I should at least mention yesterday I did upload the latest 150.0.2 releases of #firefox & #librewolf for #slackwareaarch64. Anyone using the repos in a normal fashion would have gotten those updates by now, but if you just pull a things manually, well, I didn't mention it so maybe you didn't know. And of course, since they aren't even mentioned on my website, you may not know I build them at all... good grief.
Replying to
@01micko@aus.social @thesaigoneer@social.linux.pizza @dobbie003@fosstodon.org sometimes flatpaks have either odd perms or missing support. It depends a lot on if it’s an official package or if some rando created it. Many times though, you need to change perms and export things which generally needs another flatpak like flatseal. I’ve never tried audacity flatpak though, there’s def some odd choices here and there.
Replying to
@mason@partychickens.net yeah It'd be nice to have a clean way to curate your own install and not break it, it can be done but who has that amount of time? This is why I just use it as-is and peel off layers as I go. Locally, I don't care about hdd space, but that changes in other envirs, I need a light install for many things, and there's better distros (or BSDs) for that task. It's hard to dedicate time to something when you know it's done better elsewhere. It has to be a labor of love then.
Replying to
It's been a long time since I checked installation of it, but it does omit a lot of things (e,f,k,xap,y) from slack already, but that could really be cleaned up even more (some day) and things can still be added to it like any slack-based system. It's basically just a fucked up liveslak with homebrew & flatpak with some shit along for the ride.
Replying to
Just like my "plasma-slim" repo it only includes konsole & falkon outside of the main desktop. (well and plenty of what slack offers ouside of kde).
The goal is to not add real slack-packages to it but to use flatpaks & homebrew for extras.
I don't know if it's worth spending more time on or not. If anyone tries it, please tell me if its a worthy effort to continue and maybe I'll share more of them later ;)
Replying to
I'd not been able to get bazaar to play nice on slackware, so I figured if I have Plasma Discover instead, I don't need it anyway. I included niri and it boots to sddm but DMS needs configured before use, so in a plasma session you can run "dms setup" to configure that, then logout and choose niri and you'll have DMS going like a champ then.
Its not a production ready system, things might not even install cleanly even, but it's a fully functioning toy, hooked in to my repos out of the box.
The "LuckyCyborg" has released a Plasma 6.3.6 series of packages for #slackware 15.0. https://www.linuxquestions.org/questions/slackware-14/building-the-plasma6-for-slackware-15-0-stable-in-the-ktown-style-a-build-based-on-the-alienbob%27s-ktown-4175764168/
Bravo to him for seeing it thru but damn that looks like a mess.
Replying to
@thesaigoneer@social.linux.pizza my homemade repo experiments are kinda like labs, but in these labs we makin Frankenstein. 😂
Replying to
@thesaigoneer @gwenhael of course I use tools to automate a ton of things, but automation only goes so far for me. I prefer a human touch for many things in the end. Because things slip by automatic processes, and I notice things much easier with my eye. Like any tool, using what is comfortable and practical for oneself is the best approach. As long as you get where you're going, then thats the perfect solution!
Replying to
@thesaigoneer@social.linux.pizza oh I get it. Before I started offering packages and all that I'd just build things and make a package manually if I needed one. It wasn't until I started sharing things that I decided I should do it the "right" way, and tbh I kinda don't like it, it's less fun than stitching things together manually like a cave-man. But Slackers all have the same POV, "Show me the SlackBuild" is how they roll, but maintaining a repo with compat for current, now that's my fringe case-study lol
Replying to
@thesaigoneer@social.linux.pizza I drink my hot coffee black but cold is another story. Cold is jarring, i need sugar for that. 🤣
Replying to
@thesaigoneer@social.linux.pizza @dobbie003@fosstodon.org I do have to assume plasma 6 will be officially added soon enough to slackware and a new release will follow after that eventually. But I’ll have to keep that around for afterwards because plasma 7 and such will exist some day. 😆
Replying to
@frotz@mastodon.sdf.org oh it’s all good, it’s designed to be able to install properly as well. I’ve not tested installation in some months but I do have an install of it. Anything outside of slack comes from my package repo, so it should be as usable as anything else installed any way you’d may want.
But do look at the slackpkg blacklist, there’s some version numbers in there that effectively block plasma updates (didn’t work as I’d hoped it would) so there’s a few caveats.
Replying to
@frotz@mastodon.sdf.org excellent, very good to hear! I’ve not tested since I added functional brew to the iso but that may flake-out if installed locally. There is a script /usr/local/bin/brew-install.sh which is just a local copy of the homebrew setup script if it doesn’t actually transfer over for an install. I don’t think anything installed thru flatpak/brew will auto-install either. These are limitations I’ve not really decided how to handle. But yeah an install *should* work fine as well.
Replying to
@thesaigoneer@social.linux.pizza yeah thats a good way to do it. I create start scripts in my $HOME for things and run them from there or I have GDM run on boot if I'm going for a gnome session but that's not the norm usually.
Replying to
@thesaigoneer@social.linux.pizza none of these are much different really. Just the list of packages usually. Including it all is possible too, just seems overkill. lol (when it works)
Replying to
@mason@partychickens.net you should look at the min base lxc package list if you want a minimal slackware. I’m using that to build up a custom install for my web server to save space. The problem is I need to track every dep all the way thru for each thing I need after. Yes it’s a pita, and I agree, there needs to be something.
I’m debating moving my server to another distro. I moved email off of slack during the 14.2 cycle and even removing by tagfile the OS is still too large in a size constrained place.
Replying to
@thesaigoneer@social.linux.pizza I think I shared an iso with you months ago which was basically this but it didn’t come with brew installed then. This does— caveat is that it’s only probably usable by the live user (or uid 1000), outside of that it’s probably the same as other ISOs from me. I’ve changed very little since 😂
Replying to
The main idea here is a slack-based system (which in theory is slimmed down more than it is now) that you can still fuck up as you see fit but removing the requirement that you have to build everything you add to it (within reason). It has the same quirks as slack cuz it is slack, but slack for Pinks.
Maybe it should be called Pinkware. 😜
Replying to
oh and just like any liveslak I throw online, use Alien's "iso2usb" script if you want persistence (or else it's not really all that cool without it).
and the slackpkg blacklist file is hella fucked up, this is literally what I build for myself, mess and all. 😂
Replying to
Also, people always ask "where's the source?" it's slackware, packages from my repo (slackbuilda are there), and created with liveslak. The source is available in the places it came from, I just put puzzles together. If it turns into something real someday, sure I'll make some sort of source repo, but as it is, this is just a toy (not suitable for children under 8) also possible choking hazard.
I had reported that wifi on the pinebookpro had gone poof on kernel 6.18 series packages on slackware. As a way to sidestep missing wifi I'd built my own 6.12 kernels from an old config I'd found I had backed up.
Went I went to test/compare modules and such today and re-upgraded to kernel 6.18.... wifi just worked. Of course that would happen, makes total sense to me wifi just randomly works again.
In hindsight, what should I expect from a $200 laptop? 🫠
I had re-done and cleaned up the sloppy mess I made last fall for plasma 6 on 15.0 but after looking at it a second time, I realized there was plenty of things one should avoid on a stable system, so I just left it alone. It was fun to see it running but it seemed counter-productive to put time into such an old release at this point.
But the full experience is out there now for anyone running #slackware 15.0.
Replying to
@thesaigoneer@social.linux.pizza hehe it not so hard to turn things into a SlackBuild, overall it’s very much a formula that each build system has, it’s just applying changes for specifics in the end.
Sometimes you have to sink before you can swim. 🤣
Replying to
@thesaigoneer @dobbie003 gentoo just complicates building things from source for me. Like it’s compiling programs with training wheels. I imagine everything has a “use flag” but unless you have mapped out where you’re going, you’ll likely end up in a world of hurt if it’s not quite the detailed map. But I guess that’s where the nerd-ism comes in. 🤓
Replying to
@thesaigoneer@social.linux.pizza @dobbie003@fosstodon.org yeah I won’t use Fedora. Not a fan of it, red hat, or rpm (PTSD from late 90s). I have Debian “bananas” installed which hasn’t been booted in prob a year now but it worked fine too. The gentoo guys are directly involved in Asahi, so it’s a wise choice if wanting to install. I just lack the dedication to learn gentoo. 😂
Replying to
@thesaigoneer@social.linux.pizza @dobbie003@fosstodon.org Fedora is the main asahi distro. But there’s flavors for gentoo, Debian, arch, void, maybe even alpine by now. I used to have slackware running but I lack dedication to a single platform and basically no one cared. lol But yeah most M1/2 machines are all supported and it runs great. Would recommend.
Replying to
@remilia@social.cyberia9.org this is the only way I’ll drink iced coffee, it’s the best. The condensed milk is what makes it. Iced coffee is nothing without it. 😂
Replying to
@thesaigoneer@social.linux.pizza speaking of, one of these days I should change the package name for that. I didn’t bother because it’d create confusion, but maybe I should go ahead and do it. Hehe
I've pushed the latest #ktown for #slackwareaarch64 updates to be in sync with Alien's repository. Please ensure you install the new dep packages so nothing breaks along the way!
I updated #librewolf to 149.0.2 earlier today for #slackwareaarch64 thanks to a patch given to me by ponce (not sure if he’s on masto). https://slackware.lngn.net/
Replying to
@mrv404@mastodon.social of you’re using sudo it’ll fail everytime. Login as the superuser with “su -“ and then run the script.
So when I'd updated the OBS packages for arm64 I'd noticed that screen recording wasn't working in gnome but worked fine in plasma. So it appears the gnome session isn't starting pipewire properly any longer, as no sound device is registered. I guess I overlooked that since I prefer silence, seems I need to look into this issue. #slackaroni
I updated the #crux port overlay for #lxqt to the latest 2.4.0 release.
To use the overlay, one needs to add the 'kde-plasma-6' overlay and then 'lxqt' on top of that. Of course, LXQt supports many WMs, from openbox, xfwm4, to all the latest Wayland compositors like hyprland, kwin_wayland, sway, and even niri, as seen in the attached screenshot.
Replying to on mastodon.sdf.org
I really need to pick up a cheap ssd some day, the onboard emmc is absolutely terrible. It works, but makes the system 10 times slower than it actually is. This is almost a usable system, as long as I don't open more than 3 things and completely forget about browsing the web. 😜
Replying to
@grahamperrin@mastodon.bsd.cafe @ascreen@mastodon.sdf.org it's very nice to see so much work being done and things being addressed. It's appreciated all around!
Outside of kde, to the main #slackaroniaarch64 (sure I’ll make myself a new hashtag) I updated flatpak-1.16.6, deno-2.7.12, some evolution updates, and a rebuilt gnome-session package, feh, quickshell, lazygit updates (and more!) https://slackware.lngn.net/
Screenshots don’t seem to function yet, so I had to do it the newb way…
I feel like this is a trap…
On Reddit today I helped a slacker with a Mac and trolled a gentoo user who took 16hrs to do a bindist install to get a system with noctalia-shell.
I keep the scales balanced. 😆