Skip to content

Stripping the release tarballs #5618

@jbergstroem

Description

@jbergstroem

(refs #5612)

I think we should be a bit more aggressive as to what we bundle in the release tarballs. I see it similar to how autotools handles make dist versus using the original repo; meaning most files there for specific development won't be included - but enough files to verify the state of the binary often is (read: test suite). With this strategy most dotfiles, readme's in the root directory would go away. Additionally, I'd suggest stripping everything related to linting and introduce some minor logic in Makefile/vcbuild.bat that points people to git clone if they want to do development. Theres probably a few more things in tools/ we could strip, such as packagemaker-stuff.

Finally, @bnoordhuis suggested we bake an alternate readme that we push as part of the release packages that more accurately represents whats included and how to use it.

Thoughts? Anything else that should go?

cc: @nodejs/build, @bnoordhuis, @Trott, @jasnell

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildIssues and PRs related to build files or the CI.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions