pkg updatenormally again.
Reaction score: 578
Aww you caught me
FreeBSD donation page said:A minimum donation amount of $10 is required.
Checked the build on FreeBSD 13.0-RC4 - worked But as it is only a plain text VM… haven't seen SeaMonkey executed on it.I am going to try RELEASE-13-RC just to get a build off with python27 still around.
seamonkey-2.53.7 also work on FreeBSDHello.
I was upgrade my notebook from FreeBSD 12.1 to 12.2 and built seamonkey-2.53.6 for it.
I tested it on i386. For amd64 I only checked building it.
Yes I use that as well. Interesting thing with this new SeaMonkey we should be able to run the mainline Ublock Origin (with Firefox 60 supported) but it didn't work for me. I had to use legacy like you.But as we're talking about Addons, here's the (IMO) real interesting one - a working uBlock origin:
I have not had those problems??
though the previous version had its cookies and history and password storage all erased on restart. Wish those were documented so the
backup is easier. [ I had backups... ]
Yes it does use pulseaudio (but not alsa-plugins!). So does firefox. Else, you can compile FF with sndio for sound, but the sound will be worse than with pulseaudio.YT videos took a short break every now and then. As the related code is from Firefox I've looked into its Makefile: PulseAudio is default there, so I gave it a try.
But Firefox doesn't set PulseAudio as a dependency for the package, only to compile (same for ALSA); I'm wondering if I should do the same…: At the moment I assume that if someone says "yes, that" in the config dialog, the related audio package is wanted, too. But is it?
I found places.sqlite.corrupt just today and a four-step might-fail method to dump-restore it back to places.sqliteGoing back to an earlier version will always include the sword of Damocles of updated (and therefore non-fitting) config files etc.; So in my opinion this mustn't be documented (also this hint would appear on installing the compiled package - so running the binary out of the work directory before installing it won't do the trick). But the project website itself shows many big fat red warnings: Updating to 2.53.1 or above means "no way back" (or "use your backups"). Anyway…: I've added a clear hint on my website, too.
That makes it work for me with every `make install`. It uses my packages all right. Putting the same in /etc/make.conf doesn't.