A beta version of Vivaldi has been released recently, and it uses both a different install location, and profile directory. While the previously-released snapshots installed into /opt/vivaldi-snapshot, and used ~/.config/vivaldi-snapshot for user profile information, the beta release installs into /opt/vivaldi-beta, and uses ~/.config/vivaldi. (This, for example, leads to a bit of a surprise when you upgrade from 1.0.303.48_p1 to 1.0.303.52_p2 and find out your entire profile is empty.) It should be possible to choose a release stream to follow, even install multiple release streams at the same time, probably the same way Opera or Chrome ebuilds handle this (separate package names), or perhaps using different slots for different streams (By the way, is there some canonical explanation why this is not the approach taken with Opera and Chrome?). Reproducible: Always
There didn't seem to be a need when the Vivaldi previews and snapshots started (and for quite a while afterward). Vivaldi still seems to be simply racing toward "-stable" now. You can fix the profile issue by simply making a symlink. Splitting the ebuilds up into several packages has disadvantages, too, but I'll give it some thought.
Yesterday, Vivaldi finally hit a stable (1.0) release. How will the ebuild building continue as of now? I'd really like and appreciate different stable and -snapshot releases. Also I got to say, thank you Jeroen for putting out vivaldi-snapshots real fast after they were released by Vivaldi. Ive been using Vivaldi for a while now and were always excited to find new snapshots, but Im thinking of following a stable channel now if you make it possible. (I dont really want -snapshots anymore, but some other people might)
Hey, guys, this is maybe tangentially related, but it appears that Vivaldi's source code is available here: https://vivaldi.com/source/ I can't find any links to this from their main site, though, which is kind of weird. I stumbled across it in their forum. Any thoughts on the possibility of a source-based ebuild for vivaldi?
(In reply to Jared B. from comment #3) > https://vivaldi.com/source/ Interesting. > Any thoughts on the possibility of a source-based ebuild for vivaldi? File a new bug report, please.
*** Bug 596926 has been marked as a duplicate of this bug. ***
I think too, that it would be best if vivaldi provided different release streams, or at least find a way to automatically create symlinks. It is very frustrating not be able to see your bookmarks or the history after an upgrade.
(In reply to Petross404(Petros S) from comment #6) > It is very frustrating not be able to see your bookmarks or the history > after an upgrade. I avoided this by creating a symlink inside my .config and .cache directories. vivaldi-snapshot -> vivaldi I still dislike snapshots as they sometime break (especially with h264 support), so I used to mask >www-client/vivaldi-stable-version but now I just drag the stable ebuild into my own overlay and mask www-client/vivaldi-*::gentoo
I'd like to add my voice to requests to separate -snapshot from -stable. Although symlinking fixes the profile issues, it would help to keep multiple versions organized (and especially now that there's a stable branch, where some people may prefer to stay and others not, for various reasons). Regardless, thanks for maintaining the package. It's a good browser, so I'm glad to see it getting some care.
