Hi, I'm using www/vimb-gtk3 from latest pkg repo for 10.3-RELEASE amd64 and I'm unable to play HTML5 videos (from youtube.com for instance). After installing multimedia/gstreamer1-libav multimedia/gstreamer1-plugins-good videos can be played. It seems to me that these ports have to be added as runtime dependencies (at least for www/vimb-gtk3, but possibly for www/vimb-gtk2 too) ... Regards, kaltheat
I do not think it is good idea to add more deps, as webkit already pulls a lot of trash. Maybe mentioning them in pkg-message would work?
Are those all plugins you had to install? I have the following gstreamer1-libav gstreamer1-plugins gstreamer1-plugins-bad gstreamer1-plugins-good gstreamer1-plugins-ugly but on some occasions HTML5 refuse to work.
I've got these gstreamer pkgs installed: # pkg info -a -o | awk '{print $2}' | grep gstream multimedia/gstreamer1 multimedia/gstreamer1-libav multimedia/gstreamer1-plugins multimedia/gstreamer1-plugins-good Note that I also installed www/firefox some time ago - maybe this installed something that is needed for HTML 5 to work with vimb-gtk3 ... Regarding your idea of mentioning these pkgs in pkg-message: Do you have any usage data for vimb? Why and how do users use it? If they use it as a nearly full-feature replacement for bloated browsers like firefox or chromium, they might expect vimb to be able to support HTML5 out of the box which would mean that personally I would make these pkgs real run-dependencies. If users use it as an enhanced lynx ;) I would put some notes in pkg-message. Anyway those notes in pkg-message are preferable over nothing ...
Created attachment 169359 [details] www/vimb-gtk2 Bloated?! A month ago I built firefox out of curiosity. www/firefox had built in 01:15:08 vs. 02:19:42 for www/webkit-gtk2. Thast is an hour difference! During runtime, firefox hogs just as much (maybe more) resources, but does not: 1. Suddenly take up all virtual memory and hang on 1 our of every 3-5 sites (try https://lifehacker.com). Seriously, "pkill -9 -n vimb" is my new favourite command. 2. Crash so easily (http://zags.midural.ru). 3. "SSL handshake failed", for no obvious reason and with zero useful information on who is to blame and what to do (https://lk.rt.ru). Ok, the last 2 sites might have sloppy devs or admins, but that is not an excuse. Then I do not even theoretically know how this engine works well (but it does) on Mac Safari. Maybe different library with the same name, or some proprietary band-aids to make this one work. </rant> Anyway, as for usage, I do not have any statistics, but vimb aims to be full-featured browser. I think I will add optional depends.
Created attachment 169360 [details] www/vimb-gtk2: portlint -AC
Created attachment 169361 [details] www/vimb-gtk2: poudriere testport
Geez, turned out Firefox only took 2 hours to build because of ccache. These things are equally monstrous. I added the HTML5 option when updating: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220848
Looks like this was solved by PR 220848