Emerging firefox-63 with bindist USE

[Sakaki]

Hello,

I have been trying to build www-client/firefox-63.0.1-r1 for my gentoo-on-rpi3-64bit project, which has a backing weekly-autobuild binhost. However, unlike other major versions of firefox, this one won't build under bindist USE, which is obviously mandatory for my situation.

Looking into this, firefox-63 has added a dep on >=net-libs/nodejs-8.11.0 in its ebuild (63.0.1-r1, here), when compared with earlier major version ebuilds. In turn, nodejs (both 8.12.0 and 9.11.2) specifies:

Code: Select all

        ssl? ( >=dev-libs/openssl-1.0.2n:0=[-bindist] )

and nodejs (for both versions) also has a dep on >=net-libs/nghttp2-1.32.0. In turn, both acceptable in-tree versions of that package (nghttp2-1.33.0 and 1.34.0) specify:

Code: Select all

!libressl? ( >=dev-libs/openssl-1.0.2:0=[-bindist,${MULTILIB_USEDEP}] )

However, given that dev-libs/openssl-1.0.2p includes the partial Fedora EC patchset, I wondered if this bindist restriction was really necessary. So I modified (in an overlay) nodejs-9.11.2 thus:

Code: Select all

        ssl? (
                || (
                        ~dev-libs/openssl-1.0.2o:0=
                        ~dev-libs/openssl-1.0.2p:0=
                        >=dev-libs/openssl-1.1.0:0=[-bindist]
                )
        )

and nghttp2-1.34.0 thus:

Code: Select all

        !libressl? (
                || (
                        ~dev-libs/openssl-1.0.2o:0=[${MULTILIB_USEDEP}]
                        ~dev-libs/openssl-1.0.2p:0=[${MULTILIB_USEDEP}]
                        >=dev-libs/openssl-1.1.0:0=[-bindist,${MULTILIB_USEDEP}]
                )
        )

(I also have the 1.0.2o openssl in the overlay for ~arm64 use, hence the extra variant), and with this firefox-63.0.1-r1 was able to build, and appears to run fine.

I think the same issue will apply for all arches, so am posting here rather than in the ARM forum, but my question is: is there any reason why nodejs or nghttp2 should not be usable with dev-libs/openssl-1.0.2p[bindist], given the Fedora hobbled-EC patch is applied?

[ct85711]

Just to make sure, do you know what bindist use flag means? The use flag means you want to distribute binary copies of those packages on the internet, this DOES NOT mean you want to use the precompiled package. In general, a lot of packages do NOT compile nicely with the bindist use flag enabled. The reasoning is on like openssl, in that is disables multiple encryption methods that other packages need (disabled as in those methods removed without alternative uses). While, bindist use flag on firefox is mostly harmless in its self, as that just changes the name/images for the package.

[Sakaki]

Just to make sure, do you know what bindist use flag means?

Yes, apologies if I didn't make the context clear - the point is, I want to post the resulting tbz2 in the project's public binhost (https://isshoni.org/pi64pie), so I need bindist set (as with all the other packages on there).