Reference to GPL license remains in source file

[petergrau]

With #32 my understanding is that the valid license is MIT. However in this file (https://github.com/glejeune/node-graphviz/blob/master/lib/ext/gvpr/dot2js.g) there is still a GPL license referenced. Can that be removed as well?

[dubzzz]

@glejeune Is there a motivation to keep a dependency towards a GPL script?

It seems that keeping this GPL-licensed script bundled into the published package mark the package as GPL. NPM registry flags the package as GPL, see: https://www.npmjs.com/package/graphviz.

[joechrz]

Bumping this issue as well. Graphviz continues to effectively be GPL due to this file.

[VReichelt]

A new MIT-only release on npm would really be helpful. Thanks!

[Jolg42]

Since this issue is open since now 2 years I thought that republishing to npm with a mention in the README would be a good solution, so here it is https://www.npmjs.com/package/graphviz-mit

Warning that I do not plan to maintain it, I just cloned the project, added a line in the README and ran npm publish.

[WernerClemens]

The new package graphviz-mit has a package.json with MIT license, but unfortunately this does not solve the two problems from the beginning of this issue-thread raised by @petergrau and @nemtsov

1. In this file (https://github.com/glejeune/node-graphviz/blob/master/lib/ext/gvpr/dot2js.g) there is still a GPL license referenced. Can that be removed as well?
2. The wonderful module madge has as dependency the graphviz (and not the graphviz-mit) and madge can not be used in context where GPL is not allowed. Note, madge and all other dependencies have MIT license.

As @VReichelt said:
A new MIT-only release [of graphviz] on npm would be really helpful. Thanks!