Ticket #31353 (closed enhancement: fixed)
npm: build from release tarball instead of git
| Reported by: | ryandesign@… | Owned by: | ciserlohn@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | Cc: | ||
| Port: | npm |
Description
I'm breaking this request out of #31315.
npm currently fetches from git, but the developer of npm suggests that we should really be fetching the release tarball. This would obviate the need for us to manually build the documentation, allowing us to simplify the port again by undoing most of what was done in r84119, r84252, and r84253. Unless there's a reason I don't know about why we're building from git, we should use the release tarball.
Change History
Note: See
TracTickets for help on using
tickets.
I don't remember the details but back when I did the first port of npm I had some trouble with the release tarball. So I went for the git-fetch & make route. This was unproblematic (expect that always fetching the sources with git is somewhat inefficient) so there was no reason to change that. As there are now some problems with building the docs and the npm developer suggest using the release tarball I'll have another look at using the release tarball for the port. Please have a little patience.