Flatpak support
-
@Khlydo WIR. We give no timeline.
-
Just to share my perspective,
I will start using Vivaldi full-time both for personal and professional workload on my workstation if Vivaldi is officially packaged as a Flatpak too.
This is the only setback there is for me.
-
thinking about this issue as i scrolled down the last couple of dozen posts to get a feel for the thread, and knowing that over recent months i've been getting more interested in immutable distros like fedora silverblue/kinoite [gnome/kde, respectively] and opensuse microos [gnome,kde, others available], i wondered why people here who express impatience for a flatpak vivaldi for their own immutables, don't just do this.
create a container, eg, distrobox or podman, of whatever distro takes your fancy, in your installed immutable. install vivaldi in your container, using that distro's native pkg [eg, deb or rpm; downloadable ofc from the vivaldi site]. then once installed in the container, export the launcher to make it conveniently accessible thru your immutable's standard apps menu.
i've not yet spent time to test this, but afaik, this seems viable. anyone?
Look, you've got it all wrong! You don't need to follow me. You don't need to follow anybody! You've got to think for yourselves! You're all individuals!
-
@ybjrepnfr Flatpak is one thing but flat out NO to Distrobox or Podman.
-
@ybjrepnfr
that'll work, but is a hassle to do. Plus it's easy to simply forget to update the browser that way (potentially dangerous for a browser). Especially since a lot of those distros have a GUI way to update. Silverblue/kionite even does it automatically without bothering the user.Flatpaks on the other hand are much nicer to deal with, allowing most users to get and update apps graphically. Of course I understand that actually creating the flatpak may be difficult.
-
@MrScientific to be clear, my suggestion was only offered as a temporary workaround, for users of immutables, until such time as an official vivaldi flatpak becomes available.
-
@ybjrepnfr Using Distrobox just for Vivaldi means you'll pretty much have to maintain an entire separate distro just for one app. I mean if you already use Distrobox a lot for other stuff, then sure, it's a decent solution, but otherwise it's very inconvenient.
The temporary solution I found for myself is simply download Vivaldi rpm, open it with an archive manager, extract the Vivaldi folder from opt folder found inside the rpm and create a custom .desktop file that points to /your/directory/vivaldi/vivaldi .
Then, when Vivaldi has updates, I simply download the newer rpm, extract and replace the Vivaldi folder with the newer one.
This sounds like a lot of effort, but updating it like this takes exactly a minute, including the download (if you have a fast internet). And it's still way less effort than maintaining a Distrobox just for one app. -
Made an account to back up the idea for a Vivaldi Flatpack....I use it on all my other systems and I sorely miss it when I use my Steamdeck.
-
@MrScientific said in Flatpak support:
Especially since a lot of those distros have a GUI way to update. Silverblue/kionite even does it automatically without bothering the user.
Then that's the fault of the enduser if they doing keep on top of something so important. ANY OS that automatically updates should be adjusted so one has to update manually or avoid if it can't be adjusted.
-
@LocutusOfBorg
Sure I agree that the user has sone responsibility towards updating their own system, but it does make things easier if the user doesn't have to worry about that. Currently I do have a distrobox set up for vivaldi but a flatpack would honestly make my life easier (even if only a bit). -
@MrScientific said in Flatpak support:
do have a distrobox set up for vivaldi but a flatpack would honestly make my life easier
nothing about my earlier suggestion in any way debunked that. i merely offered peeps a workaround, until such time as fp becomes available.
note that whilst i replied to you, because your words were so salient, i'm actually addressing "others".
-
@MrScientific said in Flatpak support:
@LocutusOfBorg
Sure I agree that the user has sone responsibility towards updating their own system, but it does make things easier if the user doesn't have to worry about that. Currently I do have a distrobox set up for vivaldi but a flatpack would honestly make my life easier (even if only a bit).Sorry but NO!!!! The user should be doing the updates manually cause too many things can go wrong with automatic updates. WinBLOWS is a prime example.
-
@LocutusOfBorg A brief story about this: my parents didn't access to their PC because they didn't manage to overcome the post-update OOBE with a Local Account (the option is well hidden)
Patience Is The Key To Get The Vivaldi Spree | Unsupported Extensions | Github | w11 + Kde Manjaro + Android 13
-
@user1vivaldi said in Flatpak support:
The temporary solution I found for myself is simply download Vivaldi rpm, open it with an archive manager, extract the Vivaldi folder from opt folder found inside the rpm and create a custom .desktop file that points to /your/directory/vivaldi/vivaldi .
Then, when Vivaldi has updates, I simply download the newer rpm, extract and replace the Vivaldi folder with the newer one.Simple as that. Told a year ago.
-
@Hadden89 said in Flatpak support:
@LocutusOfBorg A brief story about this: my parents didn't access to their PC because they didn't manage to overcome the OOBE post-update with a Local Account (the option is well hidden)
Want to actually use English?
-
(Fedora Kinoite) having flatpak would be very nice, rpm package is a bit awkward since it requires a manual update on immutable systems, and the flatpak would be more easily accessible, so I'm looking forward to the flatpak.
-
@user1vivaldi said in Flatpak support:
The temporary solution I found for myself is simply download Vivaldi rpm, open it with an archive manager, extract the Vivaldi folder from opt folder found inside the rpm and create a custom .desktop file that points to /your/directory/vivaldi/vivaldi .
Hei, that's a good tip there! Taking in consideration, that Vivaldi team is finally working on flatpak, I could use your workaround while waiting for miracle to happen. Had to switch, because doing rpm-ostree every update turned me off.
-
Vivaldi is already out on the Microsoft store, it only needs to be on flatpak so I can use it on my immutable distro. Is it that hard?
Don’t let this post die, it is necessary for Vivaldi to make the jump to flatpak.
-
Please support with votes this topic that we have been requesting support for flatpak for 5 years and we have not had a response. Let’s keep insisting so that it is possible.
-
@Doc4eVer you have, of course, already read this info, haven't you...?
@Ruarí said in Upgrade to Chromium 114 – Vivaldi Browser snapshot 3023.3:
It is supported until the end of June. And 20.04 and all derivatives is supported until April 2025!
make a flatpak for them like requested (for which I'd like to see how you will include the proprietary codec...)
It could not be included for much the same reasons as in the deb, rpm. Flatpak does not make this easier, indeed it makes supporting media harder!
Security is also harder on flatpak for Chromium based distros. You must replace the Chromium sandox with zypak, which is maintained by a single person and relies on a decrepated method.
There is a reason there is not a single officially maintained flatpak from the Chromium browser manufaturers.
That is not to say we will not do it. I have made a flatpak internally whilst testing which is why I know all of this.
Look, you've got it all wrong! You don't need to follow me. You don't need to follow anybody! You've got to think for yourselves! You're all individuals!
* 
