mozjs17 @17.0.0 new Portfile

[juanrgar (Juan R. García Blanco)]

Please find attached a Portfile for mozjs17-17.0.0. to js). There're two existing ports that could provide this software; they need a version update though. These two ports are spidermonkey and spidermonkey185. mozjs17-17.0.0 ships with an updated pkg-config .pc file, and it's now called mozjs17-17.0. This is, at least, required by gjs and gobject-introspection packages.

[juanrgar (Juan R. García Blanco)]

Cc Me!

[juanrgar (Juan R. García Blanco)]

Please don't try to use this Portfile. It compiles and installs fine; you can even run the js console. However, the dylib seems to be not generated correctly. I'll update it soon.

[ryandesign (Ryan Carsten Schmidt)]

Supersedes #40017. Last time I looked into the spidermonkey situation it seemed like a good idea to create separate ports for each major version of the engine. That's why we made a separate spidermonkey185 port instead of updating the spidermonkey port, and why I think this port should be called mozjs17 perhaps, not just mozjs.

[juanrgar (Juan R. García Blanco)]

Ok. I just uploaded working Portfile. It still has not variants though. I plan to add a few ones soon, as I think mozjs has some interesting options. I've changed the port name; now it's called mozjs17, to avoid dangerous updates for future versions of mozjs.

[juanrgar (Juan R. García Blanco)]

I forgot to mention that I'd be more than happy to apply fixes to this base Portfile. This is one of the first Portfiles I've written, so it's prone to errors ;)

[juanrgar (Juan R. García Blanco)]

mozjs17@17.0.0 Portfile

[juanrgar (Juan R. García Blanco)]

Just attached a new version of the Portfile with a couple of new variants added.

[nerdling (Jeremy Lavergne)]

juanrgar: any particular reason why readline should be disabled? Do you also know when the llvm hacks are needed?

akitada: do you see any particular problems with this?