| Age | Commit message (Collapse) | Author |
|
|
|
Closes #36280.
Closes #36322.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Closes #36159.
Also includes an npm bump, some audit fixes, a rewording of my previous
OpenSSL notes. We may want to consider an npm revision, but I don’t
think it’s urgent just yet - Nobody has reported any issues updating
between the old 2.1.x branch and the new 2.3.0 branch.
Closes #36222.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Pass a list to ln_sf instead of iterating over the result of Dir[]. This
form raises an error if the second argument is not a directory.
Closes #35973.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Fixes the situation where the links would skew in the event that
man1, man3, man5 and/or man7 didn't exist. This should be pretty rare
unless from a clean system, but this will guard against the failure
at least.
Closes #35969. Closes #35971.
Signed-off-by: Tim D. Smith <git@tim-smith.us>
|
|
I goofed here on the manpage linkage and location. This fixes that
mistake. Given it’s post-install, shouldn’t be any need to regenerate
bottles or such.
Closes #35824.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Bottle the npm make install process to support clt-only installs.
Closes #35341
Closes #35748.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
This reverts commit 84813bdf42a871b5e048e07c78adebeec67b76e1.
|
|
This reverts commit 2520aa3c7fb8bf199fd39f76930d6dcc632c234b.
|
|
|
|
Bottle the npm make install process to better support clt-only
installs.
Closes #35341
Closes #35738.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
An `npm` bump and general formula revision. The latest `npm` squashes a
small bundle of race conditions around git dependencies, so it’d be
good to push this into users’ hands more immediately than the next Node
release, hence the revision.
This essentially follows the new Homebrew Node guidelines of update and
revision big, ignore little, bump whatever is available when there’s a
Node update out.
Also fixes a bug around manpages and weird names causing breakage,
because there are still people out there who prefer to not follow
manpage naming conventions. Whole bundle of other smaller, less
consequential documentation updates.
Closes #35480.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Conflicts:
Library/Formula/node.rb
|
|
|
|
Version bump.
Deals primarily with the issue of Node refusing connections to AWS
services based on untrusted certs as of the last release.
See https://github.com/joyent/node/pull/8904 for detail.
Closes #35223.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
|
|
|
|
Closes #35144.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
|
|
|
|
An ` npm ` version bump, and bumps the Node links to https because Node
has finally started rocking site-wide SSL/TLS :heart:.
Closes #34708.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Removes the devel block. As far as upstream are concerned, the 0.11.x
branch is pretty much done, and won’t receive further dependencies
updates, including OpenSSL. The v0.12 branch, which is our current
HEAD, is the new development branch.
Closes #34527.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Primarily an npm bump. The other element is to deal with some of the
newer HEAD developments available.
Closes #34511.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Closes #34413.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
This is the revision point previously discussed. Roughly every 4 new
npm versions, or any major developments useful to Homebrew. This
qualifies as both, particularly around the cache directory and handling
intentional or unintentional use of sudo.
Closes #34377.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Version bump for npm. 2.19 (the one after this release) is probably a
good point for a general revision, as it deals with some sudo/cache
permission issues that have cropped up semi-regularly.
Closes #34182.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
Primarily an npm bump, sans revision because the one minor version bump
isn’t worth a revision for even with our new policy. Other than that,
fixes the HEAD to actually point at the main development stream,
depreciates the enable option, adds another line of note to the OpenSSL
situation, and slightly rewords the caveat to clarify the npm install
situation.
Closes #34084.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
This change avoids setting 'loglevel' in the npm builtin npmrc file.
Setting the log level to 'verbose' is intended only for the postinstall
step and is not desired to be persistent.
Closes #33756.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Closes #33618.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Also: run `make install`, unlink any leftover manpages, set log level to
verbose, don't install the latest version of npm, don't link manpages
(as npm now does that itself).
|
|
Closes #33524.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Version bump, and merging in some of the changes from #33017.
|
|
Closes #33599.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
In case the PATH isn't setup correctly by users.
|
|
|
|
Node have finally released a devel build that isn’t vulnerable to the
last 8 months of OpenSSL bugs, so we can throw that back in. In
addition they’ve started releasing the SHA256 checksums of each package
alongside the SHA1, Progress!
Closes #32623.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
|
|
Closes #32372.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
|
|
|
|
Closes #31914.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Okay, this is part 1 of what will likely become a host of wider changes
I propose on Node to tackle the issues discussed in
[#31777](https://github.com/Homebrew/homebrew/issues/31777).
Part 1: I’ve killed the devel build. It hasn’t been updated since May,
and Node haven’t expressed any sort of haste in issuing even a new
minor bump to the devel build that fixes the rather large [OpenSSL
vulnerabilities](https://github.com/joyent/node/tree/v0.11.13-release/de
ps/openssl/openssl) in 0.11.13. At this point, my feeling is that it’s
dangerously irresponsible to leave the devel build present given those
vulnerabilities, and I’d like to see us scrap it until we see some
movement on patching those issues. This issue is open with Node
[here](https://github.com/joyent/node/issues/8000) but remains largely
ignored and dormant.
Second change: Bumps the npm version that we ship back to the latest
stable release. A minor thing, but an early step towards fixing some of
the bigger npm problems.
Third change: Changes the way we handle npm updates post-install to
specifically target the latest stable release. Our current ``` npm
update npm -g ``` has been habitually dumping people onto the alpha &
beta builds for npm, and this solution (according to the npm team)
should solve that problem permanently. Having done local testing with
this, It does indeed seem to do the job.
These are largely minor fixes to patch things over in a stable, solid
fashion till I can work out ways to avoid the Node issues we’ve been
encountering so rampantly lately.
|
|
Closes #31708.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Updates Node to 0.10.31. I've also switched the npm download to HTTPS because npm support that now (Although Node doesn't, which is weird).
|
|
This reverts commit b859a5c6a2f8fdf1c660844a8d47a321b8ddea84.
|