Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this repo really open source ? #451

Closed
guimard opened this issue Feb 12, 2022 · 5 comments
Closed

Is this repo really open source ? #451

guimard opened this issue Feb 12, 2022 · 5 comments

Comments

@guimard
Copy link

guimard commented Feb 12, 2022

Hi,

it impossible to reproduce lib/mappings.wasm build. The result given by https://github.com/fitzgen/source-map-mappings is different and doesn't work.

Why do you provide closed-source file ? Is there something hidden ?

@asdofindia
Copy link

There is a difference between a binary being not reproducible and a binary being proprietary.

It seems to me like lib/mappings.wasm can be reproduced only with the original versions of the toolchain on the original computer 4 years ago. That doesn't make it proprietary.

@kapouer
Copy link

kapouer commented May 30, 2022

Hi, like the reporter of this issue, I tried to compile source-map-mappings to get it running along with source-map.
However some source-map-mappings methods expected by source-map have not the correct names.
If there is an incompatibility between versions, it is more likely to be between source-map-mappings and source-map,
than caused by toolchain versions.

@guimard
Copy link
Author

guimard commented Jun 12, 2022

There is a difference between a binary being not reproducible and a binary being proprietary.

It seems to me like lib/mappings.wasm can be reproduced only with the original versions of the toolchain on the original computer 4 years ago. That doesn't make it proprietary.

"Original versions of the toolchain, original computer" and original own changes !

  1. This doesn't make it opensource
  2. The current compilation result is so different that there is no suggestion that the published file has any relation to the source file allegedly used

@ochameau
Copy link
Contributor

The wasm file was built in 2018 and many things changed (rust, cargo, wasm libraries and tools).
I tried very hard to try to rebuild using version from that old year, but I never managed to get the exact same binary file.
I agree with previous comment, the binary was built from sources on the other repo and nothing is hidden.

Having said that we ought to do a refresh on the wasm binary, using latest version of everything.

I'll be doing that in #465.

@ochameau
Copy link
Contributor

ochameau commented Nov 8, 2022

#465 landed.
WASM sources are now in the repo over here.
And the WASM binary has been refreshed over there.
This binary should be easily reproducible.
I mentioned the precise versions of all the environment in the commit message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants