Replaced with register-vivaldi.sh
-
-
Save ruario/ca342ff30c7c5cbe0b51f36650d65b28 to your computer and use it in GitHub Desktop.
It does not really matter so much if you choose an rpm or deb package, since an install is not taking place and thus neither the rpm
nor dpkg
commands need to be present.
It may be slightly more reliable to use the rpm because the deb package needs ar
for extraction and some distros do not install this by default. While the rpm package does rely on cpio
as part of its extraction, this is (almost always) preinstalled.
In either case, if you found that ar
or cpio
were not present, just install the "binutils" or "cpio" packages (respectively) via your package manager, before attempting to run the script again.
Wow, randomly came across this after reading a 5 year old blog post about with "Vivaldi" was dropped from the useragent. Incredibly helpful, as I was working on making a portable version of my Vivaldi ~/.config an hour ago. Been distro hopping like crazy, and I'm finally tired of losing my RSS feeds, email DBs, and note images lol
Sidenote: can my Win64 vivaldi-snapshot-bin also point at the same profile/.config?
Sidenote: can my Win64 vivaldi-snapshot-bin also point at the same profile/.config?
You mean you would have the settings on a disc that is shared between two OSes and both Vivaldi for Linux and Vivaldi for Windows would point to it?
Things will break that way in subtle and not so subtle ways, so I would not recommend it. I think sync would be a better option to be honest.
P.S. Since you are here, I will let you on to a little secret. I wrote this for my own use because as a Vivaldi employee I have access to a constant stream of new builds and this is easier than installing on various test machines (Virtual or otherwise), not least on non rpm/deb based distros.
That said, I actually made a slightly better solution for public builds. When the builds are uploaded (by a script I wrote) I convert them on the fly to generic tar packages, which include an installer/uninstaller (plus a couple of ways to run them without installing). These packages are not publically listed on the website because they are non official (and hence not really supported) but if you know the current version number you can guess the URL, e.g. as I write this stable is version 6.1.3035.100 and thus:
https://downloads.vivaldi.com/stable/vivaldi-stable-6.1.3035.100-x64.tar
P.P.S. Be sure to read the README.md ;)
Oh and for snapshots there is also:
https://downloads.vivaldi.com/snapshot/vivaldi-snapshot-6.2.3054.3-x64.tar
Or, linked from the blog you have:
https://downloads.vivaldi.com/snapshot/install-vivaldi.sh
which I also wrote! :P
Running it with a Vivaldi package as the only command line argument would result in the following:
This version of Vivaldi (snapshot) would now be available from Gnome, KDE Plasma, Xfce, etc. menus and launcher.