Create a new release (beta5) to be able to package it into Fedora

[X3MBoy]

I'm not a proven packager, but I'm trying to build it in Fedora's Copr. But to be able to do that (with my little knowledge) I need a "release" artifact that I can refer to in my spec file.

[con-f-use]

I'm not familiar with Fedora's Copr. and from the wording I'm not sure what you mean by '"release" artifact'. If you mean a version string, please have a look at the git tags of https://github.com/instantOS/instantOS/tags. Binaries will be of limited value, because the wm relies on a number of other internal and external tools other than it's own binary - things like the libc may be different on Fedora or have a different version, so pre-build binaries won't be reliably portable since they are not designed to be.

---

On a general note:

Please discuss porting on Discord / Telegram / Matrix / Reddit. Currently, we are in beta and target Archlinux-based distributions only here - at least officially and as the main focus. This is because of limited time and having just the one main developer. We want to avoid fragmentation and not overload @paperbenni. The goal is to get a stable 1.0 fast. Hopefully, that will free up Benni a bit more, then. Maintaining and testing a package for even just the top 5 distros is a lot of work and if it's not done right, it will turn people off from instantOS. I hope you understand.

That being said, there are efforts with Nix/NixOS (might "work" on Fedora) and Ubuntu (abandoned) and ARM, but not by the instantOS main developer and currently not in scope. Porting must be a community effort. If you want it on Fedora, you're mostly on your own for now. However, there are a growing few supportive people who might be able to help. I recommend the discord. That might be the most active.

[paperbenni]

Packages on Arch are just regular compressed tar files, you can download compiled binaries at http://packages.instantos.io/
But you should also keep in mind that to have a good experience you also need some of the other instantOS components, the WM really is just a WM. Providing binary releases on github is actually a good idea but likely won't be a thing until things get more stable. In the long run you might compile on the target distro as it's not always guaranteed that libraries are in the same places on every distro. And as confuse said, this might be better suited to the community channels. feel free to join https://discord.io/instantos and discuss things there

[X3MBoy]

Packages on Arch are just regular compressed tar files, you can download compiled binaries at http://packages.instantos.io/
But you should also keep in mind that to have a good experience you also need some of the other instantOS components, the WM really is just a WM. Providing binary releases on github is actually a good idea but likely won't be a thing until things get more stable. In the long run you might compile on the target distro as it's not always guaranteed that libraries are in the same places on every distro. And as confuse said, this might be better suited to the community channels. feel free to join https://discord.io/instantos and discuss things there

Sorry I was unclear, I wasn't talking about "binaries" but to set a point where the new "release" start and the last one is considered stable. There was one set in https://github.com/instantOS/instantWM/releases for beta2. Basically what I was needing was an URL like https://github.com/instantOS/instantWM/archive/beta2.tar.gz but if it can't be, that's ok.

Also, it's ok that the WM is just a WM, I just want to package that, since I can't package the entire OS into a distribution.

I will try to join the community.

Thanks for the answers.

[con-f-use]

Yeah, we should synchronize the tags across all the repos, I agree. Though
instantOS/instantOS is the authoritative repo when it comes to versioning. That one, unlike instantWM does have a v5 beta tag and beta 5 release. It's a beta, we don't have the usual bells and whistles of CI and no real release process or checklist to speak of, yet.
Just to make sure, you do compile the fedora binary of instantos from source for your packaging effort, right?

[X3MBoy]

Just to make sure, you do compile the fedora binary of instantos from source for your packaging effort, right?

Yes the idea is to compile de WM from source to create the Fedora RPMs