Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Binary: Removes v8 version from the dir name #541

Merged
merged 3 commits into from
Nov 15, 2014
Merged

Binary: Removes v8 version from the dir name #541

merged 3 commits into from
Nov 15, 2014

Conversation

am11
Copy link
Contributor

@am11 am11 commented Nov 15, 2014

Next, we need to reflect these changes on node-sass-binaries repo.

am11 added a commit to sass/node-sass-binaries that referenced this pull request Nov 15, 2014
am11 added a commit that referenced this pull request Nov 15, 2014
Binary: Removes v8 version from the dir name
@am11 am11 merged commit 04230cc into sass:master Nov 15, 2014
@keithamus
Copy link
Member

Is this a wise thing to do? Will the v8 API be stable enough that it'll work across many versions?

@am11
Copy link
Contributor Author

am11 commented Nov 18, 2014

Well we can't know that until later. BTW, we are using like 1% of the entire V8 API. 😜

But it's certainly better than letting the users experience this kind of issue: #535.

Don't you agree ❕ ❓ 😉

@andrew
Copy link
Contributor

andrew commented Nov 18, 2014

If we don't have a binary available we should fall back to building from source rather than just 404ing bombing out. We don't officially support 0.11.x but that won't stop people trying to use it and reporting issues with it.

@am11
Copy link
Contributor Author

am11 commented Nov 18, 2014

Cool! That can be done fairly easily with the current architecture. But with v8 version slug gone, after downloading the binary for the OS-architecture under question we test it and fallback to building unless 90% of tests are passing.

404 case should be handled in similar manner. 👍

@am11
Copy link
Contributor Author

am11 commented Nov 18, 2014

@andrew, this is exactly what's happening. I just tested it; in case of 404-not-found, it falls back to node-gyp rebuild. :)

@andrew
Copy link
Contributor

andrew commented Nov 18, 2014

Cool beans!

FYI I've got a debian wheezy virtual machine setup now, going to 🚢 a new point release later today with updated linux binaries and those recent install changes.

@am11
Copy link
Contributor Author

am11 commented Nov 18, 2014

Ops; shouldn't we wait for the "Cousin of Dragon" here https://github.com/sass/libsass/releases? 😄

Its seems like they libsass is ready and node-sass is almost there, so I guess its time to flip the switch! 😎

/cc @hcatlin, @mgreter

@andrew
Copy link
Contributor

andrew commented Nov 18, 2014

The current release is broken for lots of people, this should fix that before we go and introduce a load of other changes that will likely cause more support requests and headaches. I'd like to have a good stable version we can send people to, which is currently 1.0.3 (libsass 3.0.0).

@am11
Copy link
Contributor Author

am11 commented Nov 18, 2014

Makes sense! I will push the binaries for windows in the afternoon.

@andrew
Copy link
Contributor

andrew commented Nov 18, 2014

@am11 I'm not talking about updating libsass, there haven't been any changes in master than need new binaries for mac or windows, just fixing up the linux ones that don't work on heroku or debian.

@am11
Copy link
Contributor Author

am11 commented Nov 18, 2014

Yup I know, with the current state of our master.. There was a report that v1.2.2 isn't working with W7 32bits. Perhaps the fresh binary built with relaxed compiler options do the trick?

@andrew
Copy link
Contributor

andrew commented Nov 18, 2014

Yeah it can't hurt right!

@am11
Copy link
Contributor Author

am11 commented Nov 18, 2014

Yes only if it works! :D

jiongle1 pushed a commit to scantist-ossops-m2/node-sass that referenced this pull request Apr 7, 2024
jiongle1 pushed a commit to scantist-ossops-m2/node-sass that referenced this pull request Apr 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants