www/offline-npm: Update to 0.2.2. Mark BROKEN. Support for this project is broken with npm >= v3.x

[cpm]

Summary

• Update to 0.2.2

npm >= v3.x bundled with node >= v5 has broken this project.
preinstall script is since then called after requests to npm registry are made.
This makes it impossible for offline-npm to start as a registry server.
See BROKEN.md for detailed logs.

[cpm]

• Update to 0.2.2

[junovitch]

Be sure to review https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-noinstall.html

It sounds like this is more of a runtime issue meeting the last bullet point example for BROKEN usage:

has runtime issues on systems where it is supposed to run fine.

Is this severe enough to prevent the package cluster from actually building the port? Since this is a PORTVERSION bump as well I'm inferring that some functionality is working. It may be better to note specific broken functionality in the pkg-message if there are only a few limited things that are broken and not the whole port.

Pending your feedback before making and approval or requesting changes.

[cpm]

In D7351#153275, @junovitch wrote:

Be sure to review https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-noinstall.html

It sounds like this is more of a runtime issue meeting the last bullet point example for BROKEN usage:

has runtime issues on systems where it is supposed to run fine.

Is this severe enough to prevent the package cluster from actually building the port? Since this is a PORTVERSION bump as well I'm inferring that some functionality is working. It may be better to note specific broken functionality in the pkg-message if there are only a few limited things that are broken and not the whole port.

Pending your feedback before making and approval or requesting changes.

Well, according to the offline-npm developer it doesn't work anymore.

Yes indeed support for this project is broken with npm@3. I have made some simple tests which prove this. Seams that I overlooked something with my previous test 11days ago with offline-npm running in the background. Sorry for not having better news.

IMHO offline-npm will be removed from the ports tree if he's unable to fix it in the following release.

[junovitch]

IMHO offline-npm will be removed from the ports tree if he's unable to fix it in the following release.

Sounds good. It's approved, someone could override the broken locally if they want to try to fix it but it makes sense to not have a non-working package available from the offical repo. The port will eventually get reaped if it stays broken more than 6 months. Keep an eye on it and if upstream fixes it we can drop the BROKEN on the next update. Thanks!

[cpm]

In D7351#153277, @junovitch wrote:

IMHO offline-npm will be removed from the ports tree if he's unable to fix it in the following release.

Sounds good. It's approved, someone could override the broken locally if they want to try to fix it but it makes sense to not have a non-working package available from the offical repo. The port will eventually get reaped if it stays broken more than 6 months. Keep an eye on it and if upstream fixes it we can drop the BROKEN on the next update. Thanks!

Of course, I'll keep an eye out.

Thanks for your LGTM :)