The Nightly Wobble
Sep 14, 2025
Our first look at KDE Linux, then Chris shares the latest on Hyprvibe, while Wes braves his first install.
Sponsored By:
- Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love.
- 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps.
- Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility.
Links:
- 💥 Gets Sats Quick and Easy with Strike
- 📻 LINUX Unplugged on Fountain.FM
- nebula-manager — Unified CLI tool to manage and maintain multiple Nebula VPN servers with ease.
- Nebula - Apps on Google Play
- Texas Linux Festival 2025 - Austin, TX
- JB Meetup: Austin Unplugged Birthday Lunch Party, Sat Oct 4 - Meetup.com
- JB Meetup: Austin Unplugged Birthday Lunch Party - Colony Events
- Turnstile Coffee Beer Cocktails and Burgers - Austin, TX
- bitchat — bitchat is a decentralized peer-to-peer messaging application that operates over bluetooth mesh networks.
- Texas Linux Festival Trip Support (Fake boost)
- Jupiter Broadcasting Garage - New swag available!
- KDE Linux
- KDE Linux - KDE Community Wiki
- Announcing the Alpha release of KDE Linux
- GitHub - ChrisLAS/hyprvibe: A riced up Hyprland desktop running ontop of NixOS.
- Hyprland 0.51 dropped! — The gesture system has been reworked and is now way more flexible.
- Nixtcloud: Self-Hosted Cloud in One Command — Nextcloud with NixOS in the backend and P2P connectivity enabled
- holesail-nix: Holesail package for the Nix package manager — A comprehensive Nix package and NixOS module collection for Holesail - the peer-to-peer tunnel that lets you create instant, secure connections between devices without port forwarding or exposing ports.
- Pick: lazyssh — A terminal-based SSH manager inspired by lazydocker and k9s — but built for managing your fleet of servers directly from your terminal.
- Pick: term.everything — Run every GUI app in the terminal!
Transcript
WEBVTT
00:00:11.447 --> 00:00:16.067
Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris.
00:00:16.227 --> 00:00:16.867
My name is Wes.
00:00:17.107 --> 00:00:17.987
And my name is Brent.
00:00:18.507 --> 00:00:22.527
Hey, gentlemen, coming up on the show today, we've been giving KDE Linux a spin,
00:00:22.547 --> 00:00:24.887
and we'll give you our first impressions in just a little bit.
00:00:25.267 --> 00:00:28.807
Plus, I just made a bunch of big updates to my Hypervibe distro.
00:00:28.927 --> 00:00:33.287
Yeah, it's still a thing. And I'm going to see if we can get Wes to get it installed
00:00:33.287 --> 00:00:35.647
and up and running live during the show.
00:00:35.967 --> 00:00:39.787
In fact, during the second half of the show, he doesn't even have the whole
00:00:39.787 --> 00:00:45.147
show. Then we'll round it out with some great shout-outs, some picks, and a lot more.
00:00:45.267 --> 00:00:49.167
So before we go any further, let's say time-appropriate greetings to that virtual
00:00:49.167 --> 00:00:50.747
lug. Hello, Mumble Room. Welcome in.
00:00:50.747 --> 00:00:52.487
Hello, Brent.
00:00:53.387 --> 00:00:56.607
We got a real small on-air. And then look at that big old quiet listening up
00:00:56.607 --> 00:00:58.247
there. It's glistening with the quiet listening.
00:00:58.907 --> 00:01:01.587
That's nice. Thank you, everybody, for joining us there and in the Matrix chat
00:01:01.587 --> 00:01:02.547
and making it a live vibe.
00:01:03.067 --> 00:01:10.127
And a big shout-out to our friends at Defined Networking. Head over to defined.net slash unplugged.
00:01:10.187 --> 00:01:17.507
Go check out Managed Nebula, a decentralized VPN built on the amazing open source Nebula platform.
00:01:17.767 --> 00:01:21.607
It's a project we love. We've been following it for years, and it is so exciting
00:01:21.607 --> 00:01:25.087
to see the Managed Nebula product get to something that you can recommend to
00:01:25.087 --> 00:01:26.407
businesses, friends, and family.
00:01:26.947 --> 00:01:32.047
See, Nebula is really optimized for speed, simplicity, and industry-leading security.
00:01:32.587 --> 00:01:35.887
And Nebula has a decentralized design that you can completely self-host or you
00:01:35.887 --> 00:01:36.887
can use their managed product.
00:01:37.107 --> 00:01:40.767
So for your home lab or for a global enterprise, Nebula is ready to go and is
00:01:40.767 --> 00:01:44.887
already used in some really amazing production instances.
00:01:45.067 --> 00:01:48.607
I'm talking, let's just say there's Nebula going down the road out there.
00:01:49.827 --> 00:01:51.827
I set up my first lighthouse this weekend.
00:01:51.967 --> 00:01:53.547
Is that right? Good job.
00:01:53.787 --> 00:01:56.847
Thank you. Yeah, that's where I'm starting. I'm going to do a lighthouse and a mobile device.
00:01:57.607 --> 00:02:01.587
I did kind of cheat and I used Nebula Manager, but it was really nice.
00:02:01.587 --> 00:02:03.527
Nebula, I was, it's great actually.
00:02:03.647 --> 00:02:07.227
Nebula Manager is great because one of the things it did for me is it created
00:02:07.227 --> 00:02:10.027
a template config file that's just about ready to go.
00:02:10.147 --> 00:02:13.387
And so then I just went in there, bop, bop, bop through it in like two minutes max.
00:02:13.987 --> 00:02:17.167
And I had a lighthouse. I was like, oh, that was nothing.
00:02:17.487 --> 00:02:21.167
So I feel like the process is beginning. And then I think the next thing I'm
00:02:21.167 --> 00:02:25.127
going to set up just because this is how I roll is I think maybe there's better ways to do it.
00:02:25.347 --> 00:02:28.507
I'm open to input, but I think I'm going to set up a DNS server on the same
00:02:28.507 --> 00:02:29.607
box. That's my lighthouse.
00:02:30.067 --> 00:02:34.187
I have it do a name resolution for both Nebula and external stuff.
00:02:34.747 --> 00:02:39.627
What appeals to me is like I can build at it like this for my home lab and understand
00:02:39.627 --> 00:02:42.807
it and understand how it works. And I get access to everything.
00:02:42.987 --> 00:02:46.807
Right. But then for JB or friends or family or whatever it might be,
00:02:46.967 --> 00:02:48.667
the managed product is available for me.
00:02:49.504 --> 00:02:53.444
That I really like. I can go fully self-hosted with everything and it's not
00:02:53.444 --> 00:02:55.744
a compromise or I have the managed product.
00:02:55.924 --> 00:02:58.284
And that's something you might want to check out and just get started with.
00:02:58.364 --> 00:03:02.264
If you go to define.net slash unplugged, you get it 30 days for free on 100
00:03:02.264 --> 00:03:04.104
devices and you support the show.
00:03:04.224 --> 00:03:06.764
It's define.net slash unplugged.
00:03:07.204 --> 00:03:10.604
Nothing else offers Nebula's level of resilience, speed.
00:03:11.364 --> 00:03:14.924
It's really great. And I now have my first lighthouse.
00:03:15.244 --> 00:03:17.884
It's a moment, boys. I felt really proud. And you can do it,
00:03:17.884 --> 00:03:18.884
too. You can host your own.
00:03:19.004 --> 00:03:23.144
You can use there's a public one out there or get started with 100 hosts absolutely
00:03:23.144 --> 00:03:25.344
free with a managed product. Just no credit card required either.
00:03:25.604 --> 00:03:28.124
It's define.net slash unplugged.
00:03:30.644 --> 00:03:34.124
Well, Texas Linux Fest, October 3rd through the 4th at the Commons Conference
00:03:34.124 --> 00:03:39.244
Center in Austin, Texas, is just 18 days away, probably about 10 or so days
00:03:39.244 --> 00:03:41.064
until Brent needs to hit the road from right now.
00:03:41.184 --> 00:03:42.224
Maybe eight or five.
00:03:42.884 --> 00:03:45.944
I'm feeling more like seven, so I've got to pack.
00:03:46.104 --> 00:03:48.644
Well, you've got to think about it this way. If you've got seven or eight days
00:03:48.644 --> 00:03:52.364
to leave, then you've got four or five days to fix whatever you need to fix
00:03:52.364 --> 00:03:53.164
before you can hit the road.
00:03:53.784 --> 00:03:56.724
I still have a leaking roof, so I've got to get it going on that.
00:03:57.364 --> 00:04:00.824
We have a big update on how we're doing coming up in the show later on.
00:04:00.944 --> 00:04:04.344
We've been stacking support with the audience's help for Texas Linux Fest.
00:04:04.464 --> 00:04:05.284
It's been really awesome.
00:04:06.124 --> 00:04:10.704
And I think with the incredible support we've seen from the audience and the
00:04:10.704 --> 00:04:15.124
fact that we just ticked over our 12th anniversary, I think we should officially
00:04:15.124 --> 00:04:18.844
hold the unplugged birthday party at Texas Linux Fest.
00:04:18.984 --> 00:04:23.764
So we have a meetup on the books. If you go to meetup.com slash Jupyter Broadcasting,
00:04:23.984 --> 00:04:30.284
we have an Austin unplugged birthday party on October 4th during the 12 p.m.
00:04:30.724 --> 00:04:34.284
lunch hour. Remember that that meetup page is in Pacific time.
00:04:34.444 --> 00:04:36.684
So I put it in for 2 p.m. Pacific time.
00:04:38.586 --> 00:04:42.426
Is that right? I can't remember, but I put it in. So it equates to either way.
00:04:42.446 --> 00:04:44.586
It's at lunch during Texas Linux Fest.
00:04:44.946 --> 00:04:48.866
And there's a real nice place. It offers burgers, coffee, beer,
00:04:49.006 --> 00:04:53.966
cocktails right nearby with indoor and outdoor seating. So I think we'll just walk there.
00:04:54.646 --> 00:05:01.086
And we'll hold the 12th anniversary birthday party for Linux Unplugged on Saturday
00:05:01.086 --> 00:05:03.986
at Texas Linux Fest. It should be really fun, I think.
00:05:05.006 --> 00:05:09.546
and I think also I'm going to say grab the BitChat app while we're there on
00:05:09.546 --> 00:05:11.446
the ground why don't we all organize with BitChat,
00:05:11.966 --> 00:05:15.826
I think there's no servers required no accounts required it's just location
00:05:15.826 --> 00:05:19.946
and Bluetooth and IP based so get BitChat we'll have it linked in the show notes
00:05:19.946 --> 00:05:24.026
open source we've talked about it before could be a great way for us to just communicate that's.
00:05:24.026 --> 00:05:24.466
A good idea.
00:05:24.466 --> 00:05:28.406
As you get in the area and we do have our link we're trying to raise support
00:05:28.406 --> 00:05:32.126
to get to Texas Linux Fest we were going to do the commercial sponsoring route
00:05:32.126 --> 00:05:34.646
but nothing's really worked out and so the audience is stepping up in a big
00:05:34.646 --> 00:05:37.146
way to make sure that we can get down there and do what we do best,
00:05:37.806 --> 00:05:40.526
cover these special community events like nobody else does or can.
00:05:41.006 --> 00:05:43.646
And so we'll have a link in the show notes. You can use PayPal,
00:05:43.786 --> 00:05:48.186
Venmo, or OnChain, or Lightning to support us.
00:05:48.246 --> 00:05:52.026
And you can put a little message in there. I'm kind of playfully calling it a fake boost.
00:05:52.686 --> 00:05:57.446
You can also, of course, boost us and put a message in there for going right
00:05:57.446 --> 00:05:59.026
into our fund to get us down to Texas.
00:05:59.786 --> 00:06:03.926
And I also think you could consider picking up a VLOG identification item like
00:06:03.926 --> 00:06:05.746
a hat or a t-shirt at the Jupyter Garage.
00:06:06.066 --> 00:06:09.966
We have a couple of new ones up there that you could put on and get identified
00:06:09.966 --> 00:06:13.206
by the team right away. You can find that at JupyterGarage.com.
00:06:14.246 --> 00:06:16.086
I wonder, did we get the new hat colors on there?
00:06:16.186 --> 00:06:17.226
Ooh, good question.
00:06:17.486 --> 00:06:17.906
Yeah, I don't know.
00:06:17.906 --> 00:06:21.846
I'm getting excited already. I mean, the schedule for Texas Linux Fest is up now.
00:06:22.026 --> 00:06:26.246
It's looking good. It's looking real good. And you're on Saturday.
00:06:26.486 --> 00:06:27.166
That's right, yeah.
00:06:27.346 --> 00:06:29.366
Everybody should come see Wes's talk on Saturday.
00:06:29.546 --> 00:06:30.286
After our meetup.
00:06:32.170 --> 00:06:35.230
And then right before the after parties, which there'll probably be several of.
00:06:35.950 --> 00:06:39.130
So you could grab yourself a VLOG identification item. So that way you stand
00:06:39.130 --> 00:06:41.030
up from the crowd at jupytergarage.com.
00:06:41.230 --> 00:06:46.130
Of course, we have the booths and we have the playfully titled fake booths.
00:06:46.170 --> 00:06:48.950
If you would like to support us that way, we'll have a link for that in the show notes.
00:06:49.110 --> 00:06:51.530
And we'll have an update on how we're doing in just a little bit.
00:06:54.890 --> 00:06:58.410
But KDE hit a new release stage in this last week.
00:06:58.530 --> 00:07:01.390
And we wanted to take a look at it. We've been talking about it on and off to
00:07:01.390 --> 00:07:05.330
our bootleg members and just wanted to get everyone caught up really quickly.
00:07:05.650 --> 00:07:10.170
The KDE community that makes the Plasma desktop has also now started creating
00:07:10.170 --> 00:07:11.270
their own distribution.
00:07:11.690 --> 00:07:16.650
And it's built by the KDE project to sort of feature the Plasma desktop and Plasma technologies.
00:07:17.010 --> 00:07:21.510
And we've entered into, it's still, I guess it's not, it's alpha,
00:07:21.610 --> 00:07:23.550
but it's not alpha, alpha. I mean, how are they calling?
00:07:23.550 --> 00:07:30.130
I mean, they do call it the alpha release of KDE Linux, at least Nate did over in his blog post.
00:07:30.170 --> 00:07:33.350
It's like the next alpha, I suppose. I mean, the reason why I'm trying to make
00:07:33.350 --> 00:07:36.330
this clear is it's still early days, everybody.
00:07:36.550 --> 00:07:40.790
But it is a new operating system intended eventually to be at a spot where you
00:07:40.790 --> 00:07:41.950
could daily drive this thing.
00:07:42.030 --> 00:07:46.790
It would showcase Plasma and KDE software in the best light they feel that the developers feel.
00:07:47.390 --> 00:07:50.850
And they would try to highlight modern technologies in their Wayland and Butterfess.
00:07:51.530 --> 00:07:56.010
So I think what's notable is they're calling this a testing edition now.
00:07:56.170 --> 00:07:59.930
So it's still considered alpha, but it's at the stage where they want to get public testing.
00:08:00.770 --> 00:08:05.910
So in there right now is an unreleased version of Plasma. Plasma 6.5 is in there right now.
00:08:06.350 --> 00:08:08.850
And so you can get to play with the latest and greatest stuff that way.
00:08:09.250 --> 00:08:13.170
And I know immediately you're probably thinking as you listen to this, boys,
00:08:14.414 --> 00:08:19.534
Why do we need another Linux distro? Why? Well, this is what the KDE project says.
00:08:19.794 --> 00:08:22.994
They say, quote, KDE is a huge producer of software.
00:08:23.434 --> 00:08:26.554
It's awkward for us not to have our own method of distributing it.
00:08:26.914 --> 00:08:32.234
Yes, KDE produces open source that others distribute, but we self-distribute
00:08:32.234 --> 00:08:35.534
our apps on app stores like FlatHub and the Snap Store and Microsoft stores.
00:08:35.774 --> 00:08:41.054
So I think it's natural for us to have our own platform for doing that distribution too.
00:08:41.494 --> 00:08:45.994
And that is an operating system. and so that's kind of what they say now brent there's neon though.
00:08:45.994 --> 00:08:49.034
Yeah nate has some words here about neon because well
00:08:49.034 --> 00:08:52.034
if you remember that was the old version or
00:08:52.034 --> 00:08:55.014
oof am i supposed to call it that but that was the version
00:08:55.014 --> 00:08:59.894
of linux that they were putting out for developers and those of us who are i
00:08:59.894 --> 00:09:02.774
don't know interested in finding bugs to give it a shot chris you were running
00:09:02.774 --> 00:09:08.274
that for a long time in studio too yeah indeed at least nate says kd is not
00:09:08.274 --> 00:09:13.374
cancelled however it has shed most of its developers over the years, which is problematic,
00:09:13.714 --> 00:09:17.534
and it's currently being held together by a heroic volunteer.
00:09:18.094 --> 00:09:22.954
While Neon continues to exist, KDE Linux therefore does represent duplication.
00:09:23.274 --> 00:09:26.914
As for unnecessary, I'm not sure about that.
00:09:27.454 --> 00:09:32.834
Harold, myself, and others feel that KDE Neon has somewhat reached its limit
00:09:32.834 --> 00:09:34.654
in terms of what we can do with it.
00:09:34.874 --> 00:09:41.134
It was a great First product that KDE distributed some software and prepared
00:09:41.134 --> 00:09:43.954
the world for the idea of KDE in that role.
00:09:44.174 --> 00:09:46.814
And it served admirably for about a decade.
00:09:47.314 --> 00:09:52.574
But technological and conceptual issues limit how far we can continue to develop it.
00:09:52.754 --> 00:09:56.394
I mean, I can definitely understand preferring, even in an alpha,
00:09:56.614 --> 00:09:58.174
what they've got going now to develop.
00:09:58.816 --> 00:10:01.796
to putting things together the way Katie Neon did. That said,
00:10:02.256 --> 00:10:03.936
I mean, I ran it for years.
00:10:04.156 --> 00:10:06.876
We ran it at the studio for years. It really did work well.
00:10:07.116 --> 00:10:10.736
Yeah. Yeah, I think during his heyday, it was actually a really great showcase.
00:10:11.456 --> 00:10:16.056
I guess I do empathize with the idea of that was our V1 and this is our V2.
00:10:16.676 --> 00:10:18.276
I can kind of connect with that.
00:10:18.416 --> 00:10:22.056
And it feels like, you know, designing something like this 10 years ago versus
00:10:22.056 --> 00:10:27.376
designing it in, you know, with modern applications and construction in mind.
00:10:27.376 --> 00:10:29.596
Of course, they're going to come up with a very different product.
00:10:29.896 --> 00:10:33.396
All right, BigPain. So they keep saying it's a modern, it's a modern design.
00:10:33.796 --> 00:10:38.216
What do they mean when they're saying it's modern? What does that mean in today's Linux distro parlance?
00:10:38.696 --> 00:10:42.496
Yeah, we do live in an interesting time where people are building all kinds
00:10:42.496 --> 00:10:44.476
of new wacky different versions of Linux.
00:10:44.856 --> 00:10:49.516
This is not using OS Tree or Bootsy like we've seen over, like when we talk
00:10:49.516 --> 00:10:50.996
about our uBlue friends.
00:10:51.856 --> 00:10:55.796
I guess they're using Arch as a base, but then they're using a tool called Make
00:10:55.796 --> 00:11:00.316
OSI that produces like a operating system image file.
00:11:00.536 --> 00:11:06.596
And then under the hood, you get a ButterFS main partition with a system sub-volume
00:11:06.596 --> 00:11:08.736
that is your sort of like writable world.
00:11:09.116 --> 00:11:14.856
And then they're using EROFS, which is like a read-only file system that the
00:11:14.856 --> 00:11:17.076
kernel has a modern take on that.
00:11:17.256 --> 00:11:23.276
And so they ship these images that they build as these EROFS read-only file
00:11:23.276 --> 00:11:27.636
systems that get put on your file system and managed by systemd with updatectl
00:11:27.636 --> 00:11:30.016
and there's a whole suite of systemd tools for this.
00:11:30.176 --> 00:11:36.216
Right, so you update with systemd. That's crazy. It's fun. It's not the best UI, but it's fun.
00:11:36.296 --> 00:11:38.776
And then, of course, that can hook into the systemd boot stuff.
00:11:38.796 --> 00:11:42.456
Right now, this does only work on UEFI systems and so you can have the A,
00:11:42.556 --> 00:11:44.656
B, different versions that you can roll back to.
00:11:45.316 --> 00:11:48.676
And there's a lot to like in terms of you really just download a new file system
00:11:48.676 --> 00:11:52.736
image onto your hard drive, gets kind of rigged up a little, just a little bit,
00:11:52.956 --> 00:11:55.616
connect a few dots, and then it seemed I
00:11:55.616 --> 00:11:58.476
did I was doing some poking mostly because
00:11:58.476 --> 00:12:01.496
it foils a lot of like the sort of kegs xf
00:12:01.496 --> 00:12:04.676
I like to do they do actually load the pmem module that
00:12:04.676 --> 00:12:07.356
I needed in the init ram fs already which I had to extract out of
00:12:07.356 --> 00:12:11.836
the unified kernel that they uh boot but they're using something where basically
00:12:11.836 --> 00:12:17.256
systemd systemd boot passes an efi variable that tells it which drive it booted
00:12:17.256 --> 00:12:20.796
from and then it can just use the gpt partitioning to figure out what your root
00:12:20.796 --> 00:12:24.976
is automatically and it sort of like auto generates these mount units for you.
00:12:25.236 --> 00:12:30.376
And then on top of that, KDE Linux is making sure that this EROFS,
00:12:30.596 --> 00:12:33.536
so it's like it mounts the ButterFS system as your actual root,
00:12:33.576 --> 00:12:37.396
but then immediately before you ever get anywhere, it mounts this read-only
00:12:37.396 --> 00:12:39.596
to just the slash user part.
00:12:40.156 --> 00:12:42.776
And so all of that comes from their pre-built images.
00:12:43.396 --> 00:12:45.836
Ah, and where you're living is in the sub-volume.
00:12:46.316 --> 00:12:49.876
That's where stuff like Etsy and other places that you can write to.
00:12:50.056 --> 00:12:51.516
Is home in there too in the sub-volume?
00:12:51.596 --> 00:12:51.716
Yeah.
00:12:53.012 --> 00:12:56.232
Yeah, okay. That's actually a pretty clever way to lay it out.
00:12:56.552 --> 00:13:00.052
I like that when I looked at it first, I thought, oh, okay, they didn't do home
00:13:00.052 --> 00:13:02.192
as its own partition. No, no, because it's in that sub-volume group.
00:13:02.552 --> 00:13:05.692
And, you know, they actually listed explicitly things like Nix or other tools
00:13:05.692 --> 00:13:09.592
like, you know, if we don't do, they were originally at some point in their
00:13:09.592 --> 00:13:13.032
design doing a fully, like, immutable, just like at root.
00:13:13.632 --> 00:13:18.052
But they felt this gave them a lot of the same guarantees, but with a little more compatibility.
00:13:18.112 --> 00:13:21.192
Although I did very quickly try to install Nix and it was kind of failing because
00:13:21.192 --> 00:13:25.252
it was trying to write under user local, I think, which was still read-only
00:13:25.252 --> 00:13:28.392
and so still was breaking some things. But I didn't try that hard.
00:13:28.732 --> 00:13:31.812
So this has been one of my questions is, and you just touched on it,
00:13:32.992 --> 00:13:34.532
who is this ultimately for?
00:13:36.252 --> 00:13:41.372
And I guess what you just alluded to is there is some flexibility in the underlying
00:13:41.372 --> 00:13:47.632
system because one of the groups they're clearly targeting is developers.
00:13:47.632 --> 00:13:52.772
They say, quote, you want to participate in KDE's QA process and find issues
00:13:52.772 --> 00:13:57.292
or early bugs, or, quote, you are a KDE Plasma developer, are some of the groups
00:13:57.292 --> 00:14:00.092
they implicitly state on their website they're targeting as developers.
00:14:00.292 --> 00:14:05.052
And so my concern is a lot of times an immutable system is a little too rigid
00:14:05.052 --> 00:14:08.292
and you end up doing everything in distro box or everything in containers because
00:14:08.292 --> 00:14:10.872
developers need tools. They need libraries.
00:14:11.092 --> 00:14:15.052
They need all the crap that they use to build their particular applications
00:14:15.052 --> 00:14:17.752
with their particular workflow, with their particular preferences.
00:14:18.632 --> 00:14:22.252
That's where an immutable distro can be a little bit of friction.
00:14:22.572 --> 00:14:25.452
And if you're trying to make something where people can come and build applications
00:14:25.452 --> 00:14:27.592
for the Plasma desktop, they're going to need to be able to,
00:14:28.533 --> 00:14:33.513
I don't know, what would be a basic closure setup for you, and could you get
00:14:33.513 --> 00:14:34.873
that working on something like this?
00:14:35.533 --> 00:14:38.533
Yeah, I mean, I do think you are probably going to run into some limits.
00:14:38.533 --> 00:14:40.873
It does support homebrew, so you can get homebrew going.
00:14:41.093 --> 00:14:44.673
It's kind of like a lot of these modern systems. If it sufficiently sideloads
00:14:44.673 --> 00:14:47.733
cleanly, then you can kind of make it work maybe with some modifications or
00:14:47.733 --> 00:14:50.193
some jerry-rig support that you might need.
00:14:50.593 --> 00:14:56.033
And, of course, for a lot of stuff, especially with KDE, there's flat packs are very first class.
00:14:56.033 --> 00:14:59.713
so even if you want to develop some on kde software because
00:14:59.713 --> 00:15:02.613
they do have a section in their wiki that kind of addresses like well
00:15:02.613 --> 00:15:05.913
here's how you might go about developing non-kde software
00:15:05.913 --> 00:15:08.913