Allow using an enterprise artifactory.

[ilatypov]

Revert to using a deep remote path so that the local artifactory can host gyp binaries of different packages.

[ilatypov]

The small change in node-pre-gyp will allow to use a single .npmrc variable to host binary requisites for many packages in one enterprise artifactory.

mapbox/node-pre-gyp#416

[recrsn]

Reverting to a deep remote path will block the usage of node-pre-gyp-github. We use it to automatically deploy binaries from CI

[ilatypov]

By "deep" remote paths I meant not ignoring any part of remote_path but allowing host to have its own root path. A change I suggested in node-pre-gyp will allow that and will agree with existing remote_path values not starting with a slash.

The suggested change in node-pre-gyp will change the install behaviour of a supposedly small number of consumers of existing packages that fall into the following trap,

• their remote_path value starts with a slash and
• their host override via PACKAGE_binary_host_mirror has a non-empty root path.

The install behaviour of these packages will change from erasing the root path in PACKAGE_binary_host_mirror to honouring it.

mapbox/node-pre-gyp#415

mapbox/node-pre-gyp@dffeb29

Existing versions of bcrypt will not change their install behaviour unless their consumer defines a bcrypt_binary_host_mirror with a non-empty root path and happens to use v2.0.1 of bcrypt whose use of the current node-pre-gyp erases the root path at install time.

https://github.com/kelektiv/node.bcrypt.js/blob/v2.0.1/package.json

[recrsn]

@ilatypov I'm considering using https://github.com/prebuild/prebuild. Will it be able to solve your use case? See the prebuild-install module. It contains configuration switches which is similar to your case.