They didn’t. LibreOffice devs wanted to provide support exclusively through Flatpak. Thus making native installations not supported. In stead of spending time on maintaining native package they just tell users to use Flatpak. https://lists.fedoraproject.org/archives/list/[email protected]/thread/46ZZ6GZ2W3G4OJYX3BIWTAW75H37TVW6/
Dang, that’s lame. I guess it’s up to users to adapt LO to their distro.
why is this lame?
Many like myself don’t like the old idea of downloading stuff that “just runs”. It’s too much going back to the old ways with windows where you randomly just downloaded a binary off a website and ran it.
Basically it’s the equivalent of sideloading apps on mobile devices. I won’t do that either unless it is required.
Now I do have one such app, in appimage which is my preference anyway. KDEnlive, which I run as an appimage Vs the Debian package only because I’m on Debian 10 on my main machine and have yet to pencil in the upgrade time.
Now, GNU Guix is interesting. Cryptographically secure and verified compilation (or pre-compilation) of source code straight from GitHub etc. Now, that will be more like it!
You wouldn’t go to a website and download something (unlike AppImage), you would install it through Flatpak.
Appimage IS an attempt to bring windows style software (mis)management to windows. Flatpak is more like bringing android style app management along with limited permission sets, permission portals, and some sandboxing. It also leverages the server spaces container principals more and more to do!
Guix is also super cool! In fact using guix to build OCI containers and flatpaks to me is natural evolution of the declarative/reproduce able image concepts introduced by both.
He’s a flatpak reactionary, probably an arch user.
deleted by creator
Not all Arch users are the same I guess.
I use arch btw
I mean, flatpaks are cool and all, but native packaging of distro repos is the non plus ultra for me.
possibly artix, without any init system (he start processes by hand)
Im a redhat user, and also dislike flatpaks, snaps, and allat. The only sane “uber package” is appimage and I’m tired of pretending it’s not.
Well yes, that’s usually how it happens
Short version: no they didn’t.
Long version: maybe. Fedora is no longer compiling rpm versions of libreoffice. This is a good thing. There is already a flatpack available, and this is the recommended route to getting the latest and greatest version. Additional this saved dev time from pointlessly compiling packages that are already available as flatpacks. However they are also taking people off libreoffice development and onto other things like HDR support and wayland issues. This will in the long term hurt libreoffice. To be honest, on balance this is probably a good thing.
Libreoffice is a great personal office environment, however it’s sorely lacking for enterprise use, where MS office compatability, multi user simultaneous collaboration and power user features (powerquery etc) are king. Things that libreoffice, with the greatest respect, sucks at.
Given this and that fedora is an upstream for RHEL, it doesn’t make sense for Redhat to put effort into an office suite its consumers won’t use, in favour of making other desktop features that users will use better instead.
Fedora is no longer compiling rpm versions of libreoffice.
Yes, we are. The latest build was two days ago.
Fedora is a community distro. Any software that follows the packaging guidelines can be packaged by whoever is willing to maintain it. Fedora doesn’t block people from maintaining RPMs just because a flatpak is a available, like Canonical does with snaps in Ubuntu.
Previously, the RHEL LibreOffice maintainers also maintained it in Fedora. This is common for the subset of Fedora packages (~10%) that are also in RHEL. RHEL deprecated LO, meaning it’s still in current RHEL versions but won’t be in a future major version. Because of that the RHEL maintainers orphaned the Fedora package and its dependencies. Pretty much immediately, Fedora community members adopted the packages to keep them around. This isn’t the first time this has happened, and it won’t be the last.
Good point well made. I should have been specific by pointing out that it’s only the Redhat devs that are no longer packaging RPM versions, the community is obviously free to maintain any packages it wishes (within project rules), and have adopted LibreOffice.
No worries, there is a bit of nuance to it that can be easy to mix up. People often make the mistake of thinking Fedora == Red Hat. Red Hat folks are certainly involved, but Fedora does have a healthy amount of independence too. The best example of this is the fact that Fedora uses btrfs as the default filesystem, while it’s disabled entirely in RHEL.
Long version: maybe. Fedora is no longer compiling rpm versions of libreoffice. This is a good thing.
Whi is it a good thing?
They can spend that time doing other things to help the distro.
Fedora didn’t do anything to Libreoffice. Red Hat had been the maintainer for the Libreoffice packages in Fedora up until a couple of weeks ago. The package became an orphan, and without anyone to maintain it, would end up being dropped from the distribution. For the time being, it looks like some people from the community have stepped up to maintain Libreoffice in Fedora.
So unless something happens and the current maintainers are unable to keep up, nothing should happen to Libreoffice in Fedora.
Brodie Robertson made a video about it: https://www.youtube.com/watch?v=sD-kwhRSiZo
Good for them. It seems bonkers that so much time and effort is spent by distros recompiling and packaging programs that are used across many distros.
It just makes more sense for app developers to do this work once and then just drop it on any distro and have it work.
