I do not know if may be useful or not but Vivaldi browser published it's source code.
Wow, 600+MB of sources, that's massive :)
I think they are releasing the source code just for the stable releases. Eventually we could have vivaldi (stable, source based), and vivaldi-snapshot (binary package).
I have no idea if this is viable. On top of that I don't have powerful enough hardware to build a chromium based web browser.
When building from source, they have this written in README:
# Uncomment for proprietary media codecs support.
So this could help with bug #580990 ( https://bugs.gentoo.org/show_bug.cgi?id=580990 ) as well. We could have vivaldi stable with "proprietary-codecs" USE flag?
Possible a candidate for a 'bindist' USE flag?
I used to use Opera a lot, but when they switched to use much of the chrome base, I quickly lost interest. I've yet to build the Otter variant, which, on paper, looks like it should be good - www-client/otter if you haven't seen it.
Could the Chromium team take a look at this? Since I believe the building process is similar to chromium...?
I, too would REALLY like to see this, despite the heavy resources required to build it.
This can not be done. They have published the source code for the engine (which is mostly the chromium source code), but not for their UI (which contains most of the value that they add).
I'm sorry if it had already been discussed, but shouldn't this be named www-client/vivaldi-bin then?
I remember someone saying that -bin should be appended when there's is a source version available, so in this case it doesn't matter. However there are examples in the tree with -bin name without source version available, too. I don't think there's a strict requirement about it.
Anyway back to topic, it doesn't seem like packaging the source version is possible. If you check https://vivaldi.com/source/ it only lists the major versions and not the patches. For example, the latest source was released over a month ago for 2.1.1337, while the latest release is at 2.2.1388. So not only is the source releasing lagging behind, it doesnt include the minor patches. I don't think upstream intends the source to be packaged at all, and at least at this time, it doesn't seem smart.