The second minor update to Vivaldi 2.9 is out: (1705.38)
https://vivaldi.com/sv/blog/minor-up...r-vivaldi-2-9/
Third update: (1705.41)
https://vivaldi.com/sv/blog/minor-up...r-vivaldi-2-9/

1 members found this post helpful.

That does indeed work. My only issue with it is that now I need to find a place to put any custom css files. Maybe if it were integrated into Vivaldi itself, like say a default 'custom.css' somewhere in ~/.config/vivaldi and editable (with some syntax highlighting ) from the 'Settings' it would be more appealing.

In the end, it doesn't make much sense to create a custom.css and find a location to store it for the one mod that I do.

But you have to do this one mod after every upgrade.

1 members found this post helpful.

Meh. For me, I don't use Vivaldi regularly enough to worry about upgrades. Then I only have it on my testrig, so it gets wiped out regularly.

Like I said, Maybe if it were integrated into Vivaldi itself, like say a default 'custom.css' somewhere in ~/.config/vivaldi and editable from the 'Settings' it would be more appealing.

I understand and agree with you. When using the script, the slackbuild was built. I then used installpkg to install the package, but for some reason it didn't register in /var/log/packages. As a result, when attempting to removepkg, an error was generated that was "no package found in /var/log/packages". However, when running removepkg in the directory where I stored the slackbuild it did remove the files. All I can think is that the script failed to register in /var/log/packages, or is that a responsibility the install/remove/upgradepkg tools?

FYI, there are a couple of tools which will build a slackbuild script and then also install what was built, like sbotools and sboui.

Cheers,

The same thing has happened to me more than a few times with different packages.
Have you tried using pkgtool to remove it?
Sometimes a package name is strange and I use pkgtool to look for and remove it.

Are you giving the correct package name? i.e. vivaldi-stable NOT vivaldi?

The SBo SlackBuild creates a package of the name vivaldi, while my script creates one named vivaldi-stable (like the official rpm/deb packages we produce). I had considered changing this but in the end I never really thought about it again.

Alternatively, are you running -current where the location would be /var/lib/pkgtools?

If removepkg is able to find all the files associated with vivaldi, then there are in the log, plain and simple, as it uses the log to find the files.

1 members found this post helpful.

Yes but they are tools that call the slackbuild and them call pkgtools. That is not the same as the slackbuild itself being responsible for creating log file entries and bypassing pkgtools altogether.

3 members found this post helpful.

I'm confused by the statement, it isn't making logic. If sbotools and sboui call the slackbuild, then why wouldn't slackbuild creating log file entries for insertion to /var/log/packages? Either way it seems the slackbuild, unmodified by sbotools and sboui, should create the log file.

As for the previous questions. this is on 14.2 using latest-vivaldi.sh, not -current. ls /var/log/packages/vivald* found no packages indicating neither vivaldi or vivaldi-stable were reported to /var/log/packages. Assuming I correctly understand that the pkgtools (install/remove/upgradepkg) all record to /var/log/packages and /var/log/removed_packages, but my understanding can certainly be corrected, then I'm not sure why removepkg wasn't able to find and remove the vivaldi-stable unless it was missing from /var/log/packages.

I truly appreciate your help and information. I'm now using vivaldi from SBo installed with sbotools and everything is working properly. I've decided to not use latest-stable.sh, partly because the script is lengthening, as allowed, the slackware way of naming the package and maybe that is confusing my pkgtools.

Cheers

Open any SlackBuild and look for references to /var/log/packages (or /var/lib/pkgtools) and you will find nothing because they are not involved in logging. All they do is prepare a staged copy of installable files and then call makepkg to create a compressed tar archive (Slackware package). Utilities like sbotools call the relevant SlackBuild, wait for it to complete and then call ‘upgradepkg --install-new’ with the final package name. upgradepkg in turn calls (optionally) removepkg and then installpkg. It is installpkg that makes the package log based on a listing of its contents from the output of a tar extraction (with the ‘v’ option).

So the install log is effectively created by tar (via installpkg), not the SlackBuild. It does not matter if you think this does not sound logical, you or anyone else can verify this by reading the source code for each of these (they are all just bash scripts).


removepkg uses the contents of “/var/log/packages/$PKGNAME” to remove files. If /var/log/packages/vivald* returned nothing then removepkg simply could not remove the package and yet…

Once again, you can verify how removepkg works by reading the script yourself.

And yet it did remove it, as you said yourself (previous quote above)


Have a quick check in /var/log/packages and see how many official packages are named like so: something-something-$VERSION-$ARCH-$BUILD$TAG

I put to you, that either you are doing something wrong or your system is broken. If there was actually an issue here with latest-vivaldi.sh somehow failing to create a /var/log/packages entry, don't you think that at least one other person in this thread (that is now 20 pages long) would have mentioned it?

3 members found this post helpful.

I checked my /var/log/packages and Vivaldi is there on 14.2 [and -current].

1 members found this post helpful.

I know there has been some concern in this thread with regards to network connections that Vivaldi makes back to our domains or those owned by Google. If you would like to better understand what is going on, this blog post by my colleague Yngve might help you put your mind at rest: Decoding network activity in Vivaldi

5 members found this post helpful.

On my primary work machine I don't usually use “install” Vivaldi in a traditional sense, since I have (currently) 1095 different versions available to run at the same time (for regression testing).

However, I have just run the script normally and with “VIVALDI_STREAM=snapshot” defined and installed the resultant packages. This is a 14.2 machine. Sure enough I have these entries:

3 members found this post helpful.

That is seriously good stuff! Thanks!

@ruario

I apologize for taking your time on this topic and mean no disregard to your knowledge, script or explanations. I know the slackbuild only makes the package and pkgtools writes to /var/log/packages. The one incident I asked about must be a user error. Thank you for the timely support and help. Cheers.

2 members found this post helpful.