 And now that will, well, once it finishes reloading. And now we're back to the style that it was actually showing before. So this is the new default theme for Packer 5.0, which is not yet out. And as you can see down here, I actually have the version that is generated during the package build inserted into the software at build time. So you can always see which version it is. But that's just with Fedora stuff. Like, this is actually a duplicate of a project on our internal OBS that we use that also builds not only just RPMs, but it also builds Debian packages. So you can see that this is a spec file. It's not trivial and not clean because this is building a kernel module. So everything is horrible in your soul when you do it this way. But it builds a TKMS sub package. It's got all the main stuff. It has a source package called sdabs and stuff like that. And we build for Ubuntu. There's some Susan here, Santos, Fedora, kind of the whole nice split there. And another example here would be this project here with, wow, I can't see Procdump. So Microsoft's little process dumper program for Linux. And I put this together some time ago. It's a pretty simple one. So some packages are complicated. This one is literally dead simple. All it is. The only difference here is that on the Debian side, we have to request Zlib 1G Dev. Otherwise, we request Zlib Devil. And it builds just like any other package. Most RPM macros can be added to the environment to be supported and stuff like that. So you can have fairly consistent build configurations. But yeah, let's go back to this. So aside from Datto, who else actually uses it? Obviously OpenSusa does and Pac-Man, which is their equivalent to RPM Fusion. So if you're in the Fedora community, you know RPM Fusion as the one that provides the packages Fedora can't. Pac-Man is Susan's equivalent. The Mer and Tizen projects, which are RPM-based distributions that focus on mobile. Lenaro, which focuses on ARM stuff. They have an OBS instance that's public. Dell uses OBS to actually build their Linux community packages. Though their OBS instance is not public, the repos they publish are. Collabora, if you know anything about the Debian community, Collabora is a pretty big name there. They actually use an OBS to build all of their stuff. They maintain a fork-ish of OBS for that. One name that I didn't put on here was Endless. And they also use an OBS for actually building their distribution. And Videolan also uses OBS for building their SUSA packages. But their instance is also not public. But yeah, OBS is awesome. Also kind of a little plug here. If you're interested in working on our team and doing this kind of stuff, we're hiring. So here's some references and links. And also the thing that actually makes the Debian stuff possible is this project called DebBuild. It's a monstrosity of a Pearl program that actually can process an RPM spec file, evaluate macros, and actually do proper Debian package builds out of it. So it has some extensions to the RPM grammar to support Debianisms. But otherwise, it basically works how you expect it to. So that's kind of the end of the prepared presentation part. Questions? Anything? I know I kind of ran through it kind of quickly. But I kind of wanted to make sure everybody had a chance to talk. Isn't so much a question as another similar feature I'd like to point out. So I'm maintaining a Windows port of an open source application. I have .exe binaries built from four different build systems. SegWin, MingW32 on Windows, Visual Studio, and the fourth, which is my favorite, is MingW cross compilation from the open source build service. Oh boy, yeah. There's people maintaining hundreds of MingW32, MingW64 libraries, and some binaries. And the open source build service name was going to handle all those dependencies, all those .dll libraries, and build the ultimate .exe file as a package on there reliably. It creates the build environment and tears it down. And it's going to handle those libraries too. Yep. We don't really do too much on the Windows-ish side for this. But one component of our backup and restore product actually involves having a cross-built Windows binary. And we actually do build that through our internal OBS system. Although, unlike in your case, we're actually using the Fedora MingW stack rather than the open SUSE one. But yeah, we absolutely do the same thing. And it's a really valuable thing because it makes it so that we can have a very consistent and reliable process for going from start to finish on this. And to fill in the gap with the fact that you have RPMs as output, there's a script out there called Download MingWRPM that creates a folder as a file from all the packages .exe and dll files you care about, including dependencies. Right. And in our case, we ship the package actually to live in our appliance. So it doesn't actually matter in our case because the executable has to be on the file system in some way anyway. Right. And ultimately, the open SUSE build service does have ideas for how to generate a setup that exe and all. Oh, yeah. No, they've proposed ideas, at least. There's been some bounced around ideas for at least, I think, a year or so about how to handle this, about automatically unwrapping those things and presenting them in that form. Those ideas eventually led to how they handle container images and some of the other stuff like that. But I imagine, at some point, if there's enough interest, they'll probably pull around and actually finish the stuff that they were working on for Windows as well. I mean, there was even some thoughts about how to make it so the OBS worker runs on Macs so it could produce things like Fink or MacPorts things or homebrew packages. The architecture totally allows it because it's actually written in a more or less system independent manner. It's just time, priorities. And also, Apple gets very angry when you do weird things with their operating system. Yeah, thank you. Any other questions? Great. Let's thank our speaker. Thank you, Neil. So I'd also like to remind everybody, once again, that there's a party tonight at 7. And if you've got tickets, then it's going to be the best party ever. If you can't make it, then you're missing out. But that's totally fine. Great. Thank you. Did you have any trouble setting up for us? No, it was easy. I was just surprised to know you were here. To help. Yeah, I'm surprised too, actually. I was even sure if the thing was recording or streaming or anything. I shouldn't have been about perfect. I think I got a question. Yeah. There's more of a comment than a question, but I'm not terribly surprised. I think the more you put your hands against the floor, the better the question. Yeah, that's good. So I thought I'd point out that I didn't want to seamlessly come up with any sort of application. The application is X to go. Wine's the worst. I knew exactly which one you were talking about. And post-audio is what I built. I know that, right? How did you know? Because those projects were the ones I used to figure out how to do it in the first place.