Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Mathias Bynens]

On Wed, Dec 13, 2017 at 12:45 PM, Carlos Alberto Lopez Perez <
clo...@igalia.com> wrote:

> On 12/12/17 21:18, Mathias Bynens wrote:
> >> We do not have any Linux binaries blessed, approved or endorsed by
> Apple,
> >> and we never will, regardless of what domain it's hosted on. However,
> you
> >> can get official Linux binaries from parties that own Linux ports.
> >
> > If the hosting domain doesn’t matter, would you object to it being
> > webkit.org? All I meant to say is that this would be my preference.
> >
> > Just to clarify, I’d be excited to get the downloads at all! I understand
> > who maintains the Linux port, and I appreciate everyone’s hard work on
> > this.
> >
>
> We (Igalia) as WebKitGTK+ maintainers have control over the domain
> webkitgtk.org, so we have currently the capacity to host there the
> requested files. But we don't have any control over the webkit.org domain.
>
> Also note that we only distribute WebKitGTK+ as source tarballs.
> We don't ship binaries.
>
> This binaries from the buildbot bots are not intended for third-parties
> uses. We just happen to generate them as part of a CI infrastructure.
> In any case, we are happy to make easier for you to fetch them if you want.
>

Thank you! That would be lovely, especially if
https://bugs.webkit.org/show_bug.cgi?id=180678 could be resolved at some
point by including the *.so libraries in the archives.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Carlos Alberto Lopez Perez]

On 12/12/17 21:18, Mathias Bynens wrote:
>> We do not have any Linux binaries blessed, approved or endorsed by Apple,
>> and we never will, regardless of what domain it's hosted on. However, you
>> can get official Linux binaries from parties that own Linux ports.
> 
> If the hosting domain doesn’t matter, would you object to it being
> webkit.org? All I meant to say is that this would be my preference.
> 
> Just to clarify, I’d be excited to get the downloads at all! I understand
> who maintains the Linux port, and I appreciate everyone’s hard work on
> this.
> 

We (Igalia) as WebKitGTK+ maintainers have control over the domain
webkitgtk.org, so we have currently the capacity to host there the
requested files. But we don't have any control over the webkit.org domain.

Also note that we only distribute WebKitGTK+ as source tarballs.
We don't ship binaries.

This binaries from the buildbot bots are not intended for third-parties
uses. We just happen to generate them as part of a CI infrastructure.
In any case, we are happy to make easier for you to fetch them if you want.



signature.asc
Description: OpenPGP digital signature
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Maciej Stachowiak]

> On Dec 12, 2017, at 12:18 PM, Mathias Bynens  wrote:
> 
> 
> 
> On Tue, Dec 12, 2017 at 8:52 PM, JF Bastien  > wrote:
> 
> On Tue, Dec 12, 2017 at 11:42 AM Mathias Bynens  > wrote:
> On Tue, Dec 12, 2017 at 8:38 PM, JF Bastien  > wrote:
> 
> On Tue, Dec 12, 2017 at 11:27 AM Mathias Bynens  > wrote:
> Ideally, projects such as jsvu wouldn’t have to make such decisions. They 
> would trust the maintainer of the JS engine, in this case Apple, to provide 
> the downloads. 
> 
> If Apple trusts Igalia enough, that’s Apple’s decision. Projects such as jsvu 
> shouldn’t have to duplicate that decision IMHO. The way to do that is to host 
> binaries on an official domain.
> 
> It sounds like our disconnect is on who maintains JSC outside of Apple 
> ecosystems. The GTK port is not maintained by Apple, though we work closely 
> with the maintainers and avoid breakage where we can. 
> 
> JSC is Apple’s JS engine. Who maintains which port of it is a detail that 
> downstream projects should not concern themselves with, IMHO.
> 
> Isn’t that exactly the same as the PPC or S390 versions of V8?
> https://github.com/v8/v8/wiki/Handling-of-Ports 
> 
> 
> Or the MIPS version of NaCl?
> 
> I agree this is the same. If I was building an installer that included these 
> ports, I’d prefer to get the downloads through Google/V8 too, if possible.
> 
> On Tue, Dec 12, 2017 at 8:54 PM, Maciej Stachowiak  > wrote:
> We do not have any Linux binaries blessed, approved or endorsed by Apple, and 
> we never will, regardless of what domain it's hosted on. However, you can get 
> official Linux binaries from parties that own Linux ports.
> 
> If the hosting domain doesn’t matter, would you object to it being webkit.org 
> ? All I meant to say is that this would be my preference.

I would not object. But it's not up to me. It's up to the owners of WebKitGtk 
(or another port that produces a Linux binary), and the people who would have 
to do the engineering and operations work to set it up.

If it comes down to an arbitrary preference for webkit.org  
over webkitgtk.org , then you may have to give a better 
reason to convince the people who would actually have to do the work.

Regards,
Maciej

> 
> Just to clarify, I’d be excited to get the downloads at all! I understand who 
> maintains the Linux port, and I appreciate everyone’s hard work on this. 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org 
> https://lists.webkit.org/mailman/listinfo/webkit-dev 
> 
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Maciej Stachowiak]

> On Dec 12, 2017, at 11:42 AM, Mathias Bynens  wrote:
> 
> On Tue, Dec 12, 2017 at 8:38 PM, JF Bastien  > wrote:
> 
> On Tue, Dec 12, 2017 at 11:27 AM Mathias Bynens  > wrote:
> Ideally, projects such as jsvu wouldn’t have to make such decisions. They 
> would trust the maintainer of the JS engine, in this case Apple, to provide 
> the downloads. 
> 
> If Apple trusts Igalia enough, that’s Apple’s decision. Projects such as jsvu 
> shouldn’t have to duplicate that decision IMHO. The way to do that is to host 
> binaries on an official domain.
> 
> It sounds like our disconnect is on who maintains JSC outside of Apple 
> ecosystems. The GTK port is not maintained by Apple, though we work closely 
> with the maintainers and avoid breakage where we can. 
> 
> JSC is Apple’s JS engine. Who maintains which port of it is a detail that 
> downstream projects should not concern themselves with, IMHO.

Hi Matthew,

I think you may be confused about ownership and responsibility. Let me clarify 
who owns what:

* The WebKit Open Source Project ("WebKit") is responsible for the source code 
of WebKit, including the JavaScriptCore JavaScript engine. WebKit does not have 
official releases or official binaries. Apple does much of the engineering work 
for WebKit, but we consider the open source project to be maintained 
collectively by its developers.

* Apple owns the ports for Apple platforms. We ship end-user binary releases of 
the WebKit stack for Apple platforms (macOS, iOS, Apple Windows stack). We also 
ship fortnightly binary preview releases in the form of Safari Technology 
Review. And we provide build archives for our ports, hosted on webkit.org 
.

* Other ports are owned by other entities. The Gtk port is owned by the 
WebKitGTK+ project, with much engineering and support done by Igalia. Non-Linux 
builds can be hosted on webkit.org  too, but that is up to 
port owners.


It sounds like you are asking for Apple-official JSC binaries for Linux, which 
is not something that actually exists. We do not have any Linux binaries 
blessed, approved or endorsed by Apple, and we never will, regardless of what 
domain it's hosted on. However, you can get official Linux binaries from 
parties that own Linux ports.


Regards,
Maciej___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[JF Bastien]

On Tue, Dec 12, 2017 at 11:42 AM Mathias Bynens  wrote:

> On Tue, Dec 12, 2017 at 8:38 PM, JF Bastien  wrote:
>
>>
>> On Tue, Dec 12, 2017 at 11:27 AM Mathias Bynens  wrote:
>>
>>> Ideally, projects such as jsvu wouldn’t have to make such decisions.
>>> They would trust the maintainer of the JS engine, in this case Apple, to
>>> provide the downloads.
>>>
>>> If Apple trusts Igalia enough, that’s Apple’s decision. Projects such as
>>> jsvu shouldn’t have to duplicate that decision IMHO. The way to do that is
>>> to host binaries on an official domain.
>>>
>>
>> It sounds like our disconnect is on who maintains JSC outside of Apple
>> ecosystems. The GTK port is not maintained by Apple, though we work closely
>> with the maintainers and avoid breakage where we can.
>>
>
> JSC is Apple’s JS engine. Who maintains which port of it is a detail that
> downstream projects should not concern themselves with, IMHO.
>

Isn’t that exactly the same as the PPC or S390 versions of V8?
https://github.com/v8/v8/wiki/Handling-of-Ports

Or the MIPS version of NaCl?

To be clear, folks are trying to figure out how to provide binaries despite
who owns what, but it seems like your policy is partly misguided because of
a misunderstanding.

What I’m getting at is: if GTK folks build and host binaries on the
official GTK port site, we should all rejoice.

>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[JF Bastien]

On Tue, Dec 12, 2017 at 11:27 AM Mathias Bynens  wrote:

> Ideally, projects such as jsvu wouldn’t have to make such decisions. They
> would trust the maintainer of the JS engine, in this case Apple, to provide
> the downloads.
>
> If Apple trusts Igalia enough, that’s Apple’s decision. Projects such as
> jsvu shouldn’t have to duplicate that decision IMHO. The way to do that is
> to host binaries on an official domain.
>

It sounds like our disconnect is on who maintains JSC outside of Apple
ecosystems. The GTK port is not maintained by Apple, though we work closely
with the maintainers and avoid breakage where we can.


On Tue, Dec 12, 2017 at 8:21 PM, Alexey Proskuryakov  wrote:
>
>>
>> 12 дек. 2017 г., в 10:58, Mathias Bynens  написал(а):
>>
>> Yes, there is such an expectation. jsvu has a policy of only using URLs
>> “that are controlled by the creators of the JavaScript engine”:
>> https://github.com/GoogleChromeLabs/jsvu#security-considerations
>>
>>
>> This is explained as a security policy. If the project considers Igalia
>> builds unsafe, how are the same bits copied to another domain by an
>> automated process any better?
>>
>> I'm not necessarily objecting against the copying, but trying to make a
>> legitimate story for why any extra work is needed.
>>
>> - Alexey
>>
>>
>> Anything not on *.webkit.org or similar, or anything not on on S2
>> buckets that are owned by Apple directly, does not fit that policy.
>>
>> On Tue, Dec 12, 2017 at 7:35 PM, Alexey Proskuryakov 
>> wrote:
>>
>>>
>>> 12 дек. 2017 г., в 1:34, Mathias Bynens  написал(а):
>>>
>>> It would be great to make such downloads available from webkit.org or
>>> a similar domain!
>>>
>>>
>>> Can you explain in more detail why this is important?
>>>
>>> If there is an expectation that this will make the builds more official
>>> in some way, then I'd like to understand the difference better. For
>>> example, will having links to igalia.com on webkit.org work just as
>>> well?
>>>
>>> - Alexey
>>>
>>>
>>
>>
>>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Alexey Proskuryakov]

> 12 дек. 2017 г., в 10:58, Mathias Bynens  написал(а):
> 
> Yes, there is such an expectation. jsvu has a policy of only using URLs “that 
> are controlled by the creators of the JavaScript engine”: 
> https://github.com/GoogleChromeLabs/jsvu#security-considerations 
> 
This is explained as a security policy. If the project considers Igalia builds 
unsafe, how are the same bits copied to another domain by an automated process 
any better?

I'm not necessarily objecting against the copying, but trying to make a 
legitimate story for why any extra work is needed.

- Alexey


> Anything not on *.webkit.org  or similar, or anything not 
> on on S2 buckets that are owned by Apple directly, does not fit that policy.
> 
> On Tue, Dec 12, 2017 at 7:35 PM, Alexey Proskuryakov  > wrote:
> 
>> 12 дек. 2017 г., в 1:34, Mathias Bynens > > написал(а):
>> 
>> It would be great to make such downloads available from webkit.org 
>>  or
>> a similar domain!
> 
> 
> Can you explain in more detail why this is important?
> 
> If there is an expectation that this will make the builds more official in 
> some way, then I'd like to understand the difference better. For example, 
> will having links to igalia.com  on webkit.org 
>  work just as well?
> 
> - Alexey
> 
> 


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Carlos Alberto Lopez Perez]

On 12/12/17 19:58, Mathias Bynens wrote:
> Yes, there is such an expectation. jsvu has a policy of only using URLs
> “that are controlled by the creators of the JavaScript engine”:
> https://github.com/GoogleChromeLabs/jsvu#security-considerations
> 
> Anything not on *.webkit.org or similar, or anything not on on S2 buckets
> that are owned by Apple directly, does not fit that policy.

Will an URL on the domain webkitgtk.org work for you?



signature.asc
Description: OpenPGP digital signature
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Alexey Proskuryakov]

> 12 дек. 2017 г., в 1:34, Mathias Bynens  написал(а):
> 
> It would be great to make such downloads available from webkit.org 
>  or
> a similar domain!


Can you explain in more detail why this is important?

If there is an expectation that this will make the builds more official in some 
way, then I'd like to understand the difference better. For example, will 
having links to igalia.com on webkit.org work just as well?

- Alexey

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Adrian Perez de Castro]

Hello, everybody.

On Tue, 12 Dec 2017 01:29:42 +0100, Carlos Alberto Lopez Perez 
 wrote:
> On 08/12/17 18:07, Lucas Forschler wrote:
> > If the GTK team wanted to support making these accessible,
> > they have everything they need. They could either choose to open up
> > their firewall so external folks could access them. Or, they could put
> > full archives on build.webkit.org  (which would
> > be transferred to s3/webkit build archives).
> > 
> > Maybe someone over there would be willing to take on this work if it is
> > in their budget. (Both time and bandwidth)
> >
> 
> 
> Hi Lucas, Mathias, et all.
> 
> This is bit more complex that it seems. I will try to explain.
> 
> The built products the WebKitGTK+ bots currently generate are being
> uploaded to a local server that was only reachable from the Igalia
> intranet [1]. I have just changed that, and the build products should
> be now accesible for everybody at:
> 
> http://webkitgtk-release.igalia.com/built-products/
> (also available via https if you prefer)
> 
> Keep in mind that currently we delete the built products after 10 hours,
> so don't expect to find there more than the very last few builds.
> That is just enough time for the test bots to download and test them.
> 
> We are happy on configuring a less aggressive purging of this files to
> keep them available for much longer. We can as well make this resource
> available from a more official domain (like webkit.org or webkitgtk.org)
>  
> But before doing that I will like to know if this files will be useful
> for you in the end (or not). See below.
> 
> If you download one of those build products and try to run it on your dev
> machine you are likely to have some problems with the shared libraries.
> 
> The main issue is that this binaries are linked against a bunch of libraries
> that we build in a internal JHBuild, and will likely differ from the ones
> shipped by your distro.
> 
> To test it, you can download one of this zip files and try running:
> 
> for JSC:
> LD_LIBRARY_PATH=$(pwd)/lib bin/jsc
> 
> for WebKit:
> LD_LIBRARY_PATH=$(pwd)/lib WEBKIT_EXEC_PATH=$(pwd)/bin 
> WEBKIT_INJECTED_BUNDLE_PATH=$(pwd)/lib bin/MiniBrowser
> 
> 
> Perhaps the JSC binary works because it has few dependencies (libicu and
> glib mainly), but I doubt the WebKit one will do. Your mileage may vary.

JSC binaries should indeed be easy to move from one system to another.
 
The public API in GLib has been stable for a long time, so I would not
expect it to be an issue when linking dynamically. In the case of ICU, the
public API changes now and then, and with different GNU/Linux distros
providing different versions I would expect it to be a problem.

As for WebKitGTK+ (MiniBrowsert, libwebkit2gtk, etc.) I would expect moving
the built binaries to other systems quite problematic. The only really safe
way I see is including *all* the dependency libraries from the JHBuild in the
downloadable archives.
 
> And this will be only for the 64-bit builds. Our current 32-bit buildbots
> are test ones, which means they don't currently generate and upload
> a built-product. They just test it after building it and then discard it.
> There maybe the possibility of adding an extra step to add the upload in
> case you find this built products useful.
> 
> Trying to look forward for a more elegant solution I tried to generate a
> static build of JSC with the JSCOnly port, but I failed when trying to
> link statically with libicu. I have reported that on the bug below:
> https://bugs.webkit.org/show_bug.cgi?id=180678

Statically linking the “jsc” binary would work well here, I think. Like I
mentioned above, probably dynamically linking GLib would be fine, and only ICU
needs to be statically linked for good. Then again, once we start linking
statically... what's 1 MiB more in the text section? :-)

> Let me know your thoughts.
> 
> Regards
> ---
> 
> [1]
> We do that because the server that generates the built product as well as the
> others that donwload it for testing are on the same LAN. So it makes little
> sense for us to daily upload and download gigabytes worth of data to 
> Internet, 
> when we can just serve the resources locally.
> 
> Doing that will make every build slower because then the build-only bot
> will have to wait for an upload to Internet rather than to a local server,
> as well the test-only bot will have to wait for a download from Internet. 
> Our bandwith to Internet is much less than a gigabit LAN.


pgpLTBDGExdlX.pgp
Description: PGP signature
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Carlos Alberto Lopez Perez]

On 08/12/17 18:07, Lucas Forschler wrote:
> If the GTK team wanted to support making these accessible,
> they have everything they need. They could either choose to open up
> their firewall so external folks could access them. Or, they could put
> full archives on build.webkit.org  (which would
> be transferred to s3/webkit build archives).
> 
> Maybe someone over there would be willing to take on this work if it is
> in their budget. (Both time and bandwidth)
>


Hi Lucas, Mathias, et all.

This is bit more complex that it seems. I will try to explain.

The built products the WebKitGTK+ bots currently generate are being
uploaded to a local server that was only reachable from the Igalia
intranet [1]. I have just changed that, and the build products should
be now accesible for everybody at:

http://webkitgtk-release.igalia.com/built-products/
(also available via https if you prefer)

Keep in mind that currently we delete the built products after 10 hours,
so don't expect to find there more than the very last few builds.
That is just enough time for the test bots to download and test them.

We are happy on configuring a less aggressive purging of this files to
keep them available for much longer. We can as well make this resource
available from a more official domain (like webkit.org or webkitgtk.org)
 
But before doing that I will like to know if this files will be useful
for you in the end (or not). See below.

If you download one of those build products and try to run it on your dev
machine you are likely to have some problems with the shared libraries.

The main issue is that this binaries are linked against a bunch of libraries
that we build in a internal JHBuild, and will likely differ from the ones
shipped by your distro.

To test it, you can download one of this zip files and try running:

for JSC:
LD_LIBRARY_PATH=$(pwd)/lib bin/jsc

for WebKit:
LD_LIBRARY_PATH=$(pwd)/lib WEBKIT_EXEC_PATH=$(pwd)/bin 
WEBKIT_INJECTED_BUNDLE_PATH=$(pwd)/lib bin/MiniBrowser


Perhaps the JSC binary works because it has few dependencies (libicu and
glib mainly), but I doubt the WebKit one will do. Your mileage may vary.


And this will be only for the 64-bit builds. Our current 32-bit buildbots
are test ones, which means they don't currently generate and upload
a built-product. They just test it after building it and then discard it.
There maybe the possibility of adding an extra step to add the upload in
case you find this built products useful.

Trying to look forward for a more elegant solution I tried to generate a
static build of JSC with the JSCOnly port, but I failed when trying to
link statically with libicu. I have reported that on the bug below:
https://bugs.webkit.org/show_bug.cgi?id=180678


Let me know your thoughts.

Regards
---

[1]
We do that because the server that generates the built product as well as the
others that donwload it for testing are on the same LAN. So it makes little
sense for us to daily upload and download gigabytes worth of data to Internet, 
when we can just serve the resources locally.

Doing that will make every build slower because then the build-only bot
will have to wait for an upload to Internet rather than to a local server,
as well the test-only bot will have to wait for a download from Internet. 
Our bandwith to Internet is much less than a gigabit LAN.




signature.asc
Description: OpenPGP digital signature
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Lucas Forschler]

Hi Mathias,

Apple does not maintain the linux buildbot infrastructure. We already have all 
necessary support for hosting these archives on s3 (through the WebKit Build 
Archives). The plumbing exists and is functional. It would be up to the port 
maintainers to change their infrastructure to use them. The GTK bots currently 
do extra work to AVOID putting their archives on build.webkit.org 
 and S3.  Carlos might be able to speak more to this.

Lucas


> On Dec 8, 2017, at 9:30 AM, Mathias Bynens  wrote:
> 
> Would Apple be open to providing these downloads directly? Between Igalia, 
> Bocoup, and this thread, there seems to be some demand for it
> 
> On Fri, Dec 8, 2017 at 6:23 PM, Konstantin Tokarev  > wrote:
>  
> 08.12.2017, 20:18, "JF Bastien"  >:
>> Also, as we discussed on the github bug the JSC binary is available as part 
>> of the WebAssembly waterfall that Google maintains at wasm-stat.us 
>> 
>>  
>> The build is pretty straightforward:
>> https://github.com/WebAssembly/waterfall/blob/7cda260b8ea5264900624a4cdc45df2c9e2de010/src/build.py#L943
>>  
>> 
> 
> FWIW, it's easy to extend this script to work for Windows and Linux too by 
> replacing -DPORT=Mac with -DPORT=JSCOnly
>  
>>  
>>  
>> I understand that you've got a policy of only taking "official" binaries. 
>> The GTK team would be the official maintainer of the Linux port? There's an 
>> official jsc binary is available on MacOS :-)
>>  
>>  
>> On Fri, Dec 8, 2017 at 9:07 AM, Lucas Forschler > > wrote:
>> Hi Mathias,
>>  
>> The Linux archives could be exposed on the build-archives page. In fact, we 
>> already store the output of the builders in S3. However, the igalia team 
>> only uploads a small file with a pointer to their internal builds. If I 
>> recall, they have limited bandwidth, and prefer to store their builds behind 
>> their firewall to save on external traffic to buildbot/s3.
>>  
>> If you look here 
>> 
>>  you will see a ‘transfer-to-s3’ build step.
>> The archive the builder creates is uploaded, here is a sample 
>> .
>>  
>> Opening that up shows the location where the archive is stored:
>> Built product is available here:
>> http://webkitgtk-release.igalia.com/built-products/release_r225678_b7832.zip 
>> 
>>  
>> I cannot reach that link, so I would assume it’s behind the igalia firewall. 
>> If the GTK team wanted to support making these accessible, they have 
>> everything they need. They could either choose to open up their firewall so 
>> external folks could access them. Or, they could put full archives on 
>> build.webkit.org  (which would be transferred to 
>> s3/webkit build archives).
>>  
>> Maybe someone over there would be willing to take on this work if it is in 
>> their budget. (Both time and bandwidth)
>>  
>> Lucas
>>  
>>  
>>  
>>> On Dec 8, 2017, at 12:44 AM, Mathias Bynens >> > wrote:
>>>  
>>> Dear WebKit friends,
>>>  
>>> Please consider hosting precompiled `jsc` binaries for Linux somewhere 
>>> official. Perhaps https://webkit.org/build-archives/ 
>>> ? The build bots already generate those 
>>> binaries anyway — all that’s missing is an additional build step that 
>>> archives and uploads them.
>>>  
>>> Doing so would make it easier for developers to test JSC directly, or to 
>>> include JSC when running benchmarks such as the Web Tooling Benchmark (ref. 
>>> https://github.com/v8/web-tooling-benchmark/pull/29#discussion_r155587697 
>>> ).
>>>  
>>> I recently built a tool that automates the process of installing 
>>> precompiled binaries for various JS engines: 
>>> https://github.com/GoogleChromeLabs/jsvu 
>>>  It’d be great to be able to 
>>> support JavaScriptCore on linux32 and linux64 as well!
>>>  
>>> Prior discussion: https://bugs.webkit.org/show_bug.cgi?id=179945#c11 
>>> 
>>>  
>>> Regards,
>>> Mathias
>>> ___
>>> webkit-dev mailing list
>>> webkit-dev@lists.webkit.org 
>>> https://lists.webkit.org/mailman/listinfo/webkit-dev 
>>> 
>> ___
>> webkit-dev mailing list
>> 

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Konstantin Tokarev]

  08.12.2017, 20:18, "JF Bastien" :Also, as we discussed on the github bug the JSC binary is available as part of the WebAssembly waterfall that Google maintains at wasm-stat.us The build is pretty straightforward:https://github.com/WebAssembly/waterfall/blob/7cda260b8ea5264900624a4cdc45df2c9e2de010/src/build.py#L943FWIW, it's easy to extend this script to work for Windows and Linux too by replacing -DPORT=Mac with -DPORT=JSCOnly   I understand that you've got a policy of only taking "official" binaries. The GTK team would be the official maintainer of the Linux port? There's an official jsc binary is available on MacOS :-)  On Fri, Dec 8, 2017 at 9:07 AM, Lucas Forschler  wrote:Hi Mathias, The Linux archives could be exposed on the build-archives page. In fact, we already store the output of the builders in S3. However, the igalia team only uploads a small file with a pointer to their internal builds. If I recall, they have limited bandwidth, and prefer to store their builds behind their firewall to save on external traffic to buildbot/s3. If you look here you will see a ‘transfer-to-s3’ build step.The archive the builder creates is uploaded, here is a sample. Opening that up shows the location where the archive is stored:Built product is available here:http://webkitgtk-release.igalia.com/built-products/release_r225678_b7832.zip I cannot reach that link, so I would assume it’s behind the igalia firewall. If the GTK team wanted to support making these accessible, they have everything they need. They could either choose to open up their firewall so external folks could access them. Or, they could put full archives on build.webkit.org (which would be transferred to s3/webkit build archives). Maybe someone over there would be willing to take on this work if it is in their budget. (Both time and bandwidth) Lucas   On Dec 8, 2017, at 12:44 AM, Mathias Bynens  wrote: Dear WebKit friends, Please consider hosting precompiled `jsc` binaries for Linux somewhere official. Perhaps https://webkit.org/build-archives/? The build bots already generate those binaries anyway — all that’s missing is an additional build step that archives and uploads them. Doing so would make it easier for developers to test JSC directly, or to include JSC when running benchmarks such as the Web Tooling Benchmark (ref. https://github.com/v8/web-tooling-benchmark/pull/29#discussion_r155587697). I recently built a tool that automates the process of installing precompiled binaries for various JS engines: https://github.com/GoogleChromeLabs/jsvu It’d be great to be able to support _javascript_Core on linux32 and linux64 as well! Prior discussion: https://bugs.webkit.org/show_bug.cgi?id=179945#c11 Regards,Mathias___webkit-dev mailing listwebkit-dev@lists.webkit.orghttps://lists.webkit.org/mailman/listinfo/webkit-dev___webkit-dev mailing listwebkit-dev@lists.webkit.orghttps://lists.webkit.org/mailman/listinfo/webkit-dev ,___webkit-dev mailing listwebkit-dev@lists.webkit.orghttps://lists.webkit.org/mailman/listinfo/webkit-dev  -- Regards,Konstantin ___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[JF Bastien]

Also, as we discussed on the github bug the JSC binary is available as part
of the WebAssembly waterfall that Google maintains at wasm-stat.us

The build is pretty straightforward:

https://github.com/WebAssembly/waterfall/blob/7cda260b8ea5264900624a4cdc45df2c9e2de010/src/build.py#L943


I understand that you've got a policy of only taking "official" binaries.
The GTK team would be the official maintainer of the Linux port? There's an
official jsc binary is available on MacOS :-)


On Fri, Dec 8, 2017 at 9:07 AM, Lucas Forschler 
wrote:

> Hi Mathias,
>
> The Linux archives could be exposed on the build-archives page. In fact,
> we already store the output of the builders in S3. However, the igalia team
> only uploads a small file with a pointer to their internal builds. If I
> recall, they have limited bandwidth, and prefer to store their builds
> behind their firewall to save on external traffic to buildbot/s3.
>
> If you look here
> 
>  you
> will see a ‘transfer-to-s3’ build step.
> The archive the builder creates is uploaded, here is a sample
> 
> .
>
> Opening that up shows the location where the archive is stored:
> Built product is available here:
> http://webkitgtk-release.igalia.com/built-products/
> release_r225678_b7832.zip
>
> I cannot reach that link, so I would assume it’s behind the igalia
> firewall. If the GTK team wanted to support making these accessible, they
> have everything they need. They could either choose to open up their
> firewall so external folks could access them. Or, they could put full
> archives on build.webkit.org (which would be transferred to s3/webkit
> build archives).
>
> Maybe someone over there would be willing to take on this work if it is in
> their budget. (Both time and bandwidth)
>
> Lucas
>
>
>
> On Dec 8, 2017, at 12:44 AM, Mathias Bynens  wrote:
>
> Dear WebKit friends,
>
> Please consider hosting precompiled `jsc` binaries for Linux somewhere
> official. Perhaps https://webkit.org/build-archives/? The build bots
> already generate those binaries anyway — all that’s missing is an
> additional build step that archives and uploads them.
>
> Doing so would make it easier for developers to test JSC directly, or to
> include JSC when running benchmarks such as the Web Tooling Benchmark (ref.
> https://github.com/v8/web-tooling-benchmark/pull/29#discussion_r155587697
> ).
>
> I recently built a tool that automates the process of installing
> precompiled binaries for various JS engines: https://github.com/
> GoogleChromeLabs/jsvu It’d be great to be able to support JavaScriptCore
> on linux32 and linux64 as well!
>
> Prior discussion: https://bugs.webkit.org/show_bug.cgi?id=179945#c11
>
> Regards,
> Mathias
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Boaz Sender]

This would be useful for our purposes at Bocoup as well.



On Dec 8, 2017 12:15 PM, "Mathias Bynens"  wrote:

Thank you, Lucas.

I did come across those links while looking into this but it not being
publicly accessible is a show-stopper.

Also, I’d feel better about using builds that are hosted somewhere
official, under Apple’s direct control, at least for the purposes of an
installer tool such as *jsvu*.

Apple already does this for some Windows builds, and macOS builds are
available through nightly.webkit.org. Can’t we get the same for Linux?

On Fri, Dec 8, 2017 at 6:07 PM, Lucas Forschler 
wrote:

> Hi Mathias,
>
> The Linux archives could be exposed on the build-archives page. In fact,
> we already store the output of the builders in S3. However, the igalia team
> only uploads a small file with a pointer to their internal builds. If I
> recall, they have limited bandwidth, and prefer to store their builds
> behind their firewall to save on external traffic to buildbot/s3.
>
> If you look here
> 
>  you
> will see a ‘transfer-to-s3’ build step.
> The archive the builder creates is uploaded, here is a sample
> 
> .
>
> Opening that up shows the location where the archive is stored:
> Built product is available here:
> http://webkitgtk-release.igalia.com/built-products/release_r
> 225678_b7832.zip
>
> I cannot reach that link, so I would assume it’s behind the igalia
> firewall. If the GTK team wanted to support making these accessible, they
> have everything they need. They could either choose to open up their
> firewall so external folks could access them. Or, they could put full
> archives on build.webkit.org (which would be transferred to s3/webkit
> build archives).
>
> Maybe someone over there would be willing to take on this work if it is in
> their budget. (Both time and bandwidth)
>
> Lucas
>
>
>
> On Dec 8, 2017, at 12:44 AM, Mathias Bynens  wrote:
>
> Dear WebKit friends,
>
> Please consider hosting precompiled `jsc` binaries for Linux somewhere
> official. Perhaps https://webkit.org/build-archives/? The build bots
> already generate those binaries anyway — all that’s missing is an
> additional build step that archives and uploads them.
>
> Doing so would make it easier for developers to test JSC directly, or to
> include JSC when running benchmarks such as the Web Tooling Benchmark (ref.
> https://github.com/v8/web-tooling-benchmark/pull/29#discussion_r155587697
> ).
>
> I recently built a tool that automates the process of installing
> precompiled binaries for various JS engines:
> https://github.com/GoogleChromeLabs/jsvu It’d be great to be able to
> support JavaScriptCore on linux32 and linux64 as well!
>
> Prior discussion: https://bugs.webkit.org/show_bug.cgi?id=179945#c11
>
> Regards,
> Mathias
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Hosting precompiled `jsc` binaries for Linux

[Lucas Forschler]

Hi Mathias,

The Linux archives could be exposed on the build-archives page. In fact, we 
already store the output of the builders in S3. However, the igalia team only 
uploads a small file with a pointer to their internal builds. If I recall, they 
have limited bandwidth, and prefer to store their builds behind their firewall 
to save on external traffic to buildbot/s3.

If you look here 

 you will see a ‘transfer-to-s3’ build step.
The archive the builder creates is uploaded, here is a sample 
.

Opening that up shows the location where the archive is stored:
Built product is available here:
http://webkitgtk-release.igalia.com/built-products/release_r225678_b7832.zip

I cannot reach that link, so I would assume it’s behind the igalia firewall. If 
the GTK team wanted to support making these accessible, they have everything 
they need. They could either choose to open up their firewall so external folks 
could access them. Or, they could put full archives on build.webkit.org 
 (which would be transferred to s3/webkit build 
archives).

Maybe someone over there would be willing to take on this work if it is in 
their budget. (Both time and bandwidth)

Lucas



> On Dec 8, 2017, at 12:44 AM, Mathias Bynens  wrote:
> 
> Dear WebKit friends,
> 
> Please consider hosting precompiled `jsc` binaries for Linux somewhere 
> official. Perhaps https://webkit.org/build-archives/ 
> ? The build bots already generate those 
> binaries anyway — all that’s missing is an additional build step that 
> archives and uploads them.
> 
> Doing so would make it easier for developers to test JSC directly, or to 
> include JSC when running benchmarks such as the Web Tooling Benchmark (ref. 
> https://github.com/v8/web-tooling-benchmark/pull/29#discussion_r155587697 
> ).
> 
> I recently built a tool that automates the process of installing precompiled 
> binaries for various JS engines: https://github.com/GoogleChromeLabs/jsvu 
>  It’d be great to be able to 
> support JavaScriptCore on linux32 and linux64 as well!
> 
> Prior discussion: https://bugs.webkit.org/show_bug.cgi?id=179945#c11 
> 
> 
> Regards,
> Mathias
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev