Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 581280

Summary: www-client/vivaldi - build from source
Product: Gentoo Linux Reporter: Alexandre <alexandre.guimaraes>
Component: New packagesAssignee: James Le Cuirot <chewi>
Status: UNCONFIRMED ---    
Severity: normal CC: gentoo, hydrapolic, jer, juippis, lebarondemerde, powerman-asdf
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
URL: https://vivaldi.com/source/
Whiteboard:
Package list:
Runtime testing required: ---

Description Alexandre 2016-04-26 17:28:06 UTC
I do not know if may be useful or not but Vivaldi browser published it's source code.

Reproducible: Always
Comment 1 Tomáš Mózes 2016-04-26 20:31:16 UTC
Wow, 600+MB of sources, that's massive :)
Comment 2 Alexandre 2016-04-26 20:37:46 UTC
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).

Thanks!
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2016-04-27 10:41:13 UTC
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.
Comment 4 Joonas Niilola gentoo-dev 2016-05-05 06:49:13 UTC
When building from source, they have this written in README: 
----------
# Uncomment for proprietary media codecs support.
#export GYP_DEFINES="ffmpeg_branding=Chrome"
----------

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?
Comment 5 Michael 'veremitz' Everitt 2016-05-05 09:05:06 UTC
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.
Comment 6 Joonas Niilola gentoo-dev 2016-05-23 09:15:36 UTC
Could the Chromium team take a look at this? Since I believe the building process is similar to chromium...?
Comment 7 ta2002 2017-03-19 04:47:20 UTC
I, too would REALLY like to see this, despite the heavy resources required to build it.
Comment 8 ta2002 2018-04-28 01:08:26 UTC
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).
Comment 9 Shiba 2019-01-14 08:09:47 UTC
I'm sorry if it had already been discussed, but shouldn't this be named www-client/vivaldi-bin then?
Comment 10 Joonas Niilola gentoo-dev 2019-01-15 07:21:07 UTC
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.