Skip to content

v0.10 and v0.12 node-v0.x.y-headers.tar.gz file is too big #4140

Description

@rvagg

Need to take a look at the headers tasks in Makefile and figure out why they are in the 5-7Mb range rather than 500kb. If we get this sorted out and make sure they are correct we may be able to hard-wire in some rules to node-gyp to fetch that file for certain semver ranges of v0.10.x and v0.12.x (probably won't be doing a process.release for these old versions).

Activity

  1. rvagg commented on Dec 3, 2015

    @rvagg
    MemberAuthor

    /cc @nodejs/build

  2. added
    buildIssues and PRs related to Node.js builds or CI infrastructure.
    on Dec 4, 2015
  3. richardlau commented on Dec 4, 2015

    @richardlau
    Member

    Looking at https://nodejs.org/download/release/v0.12.8/node-v0.12.8-headers.tar.gz the majority of the file size is the inclusion of bin/node and npm (lib/node_modules/npm) both of which I wouldn't expect to see in this file.

  4. richardlau commented on Dec 4, 2015

    @richardlau
    Member

    @rvagg https://github.com/nodejs/node/blob/v0.12/Makefile#L422 calls
    HEADERS_ONLY=1 $(PYTHON) tools/install.py install '$(TARNAME)' '/'
    but https://github.com/nodejs/node/blob/v0.12/tools/install.py doesn't check HEADERS_ONLY -- Looks like the tools/install.py changes from 628a3ab would need to be backported?

  5. rvagg commented on Dec 4, 2015

    @rvagg
    MemberAuthor

    That sounds right @richardlau! I didn't patch install.py in my round of backports so that would explain it. Do you care to do up a PR for this?

  6. richardlau commented on Dec 4, 2015

    @richardlau
    Member

    @rvagg Sure, I'll put together a PR. Do we want two separate PRs (one for v0.10 and one for v0.12)? Or can we make do with one and pick the change across?

  7. rvagg commented on Dec 4, 2015

    @rvagg
    MemberAuthor

    @richardlau if the change is identical then just one PR to v0.12-staging and if you can label it put "lts-watch-v0.10" and one of us will try and watch for it.

  8. jbergstroem commented on May 3, 2016

    @jbergstroem
    Member

    Was landed in #4149 to relevant branches without a "Fixes:". Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildIssues and PRs related to Node.js builds or CI infrastructure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions