Closure listing on composer/packagist

[Peter Li]

Is there any way we could get this officially listed in php composer? (packagist.org)

[Stephen Hicks]

I don't really know what that would look like - wouldn't we need some sort of PHP support?  I'm not aware of anything along those lines.

[Peter Li]

Not that I have any personal experience with this, but I think the repo needs to just linked or mirrored to packagist. and a package json file needs to be written with version information.

The google php api client is available on composer: https://packagist.org/packages/google/apiclient

There are unofficial versions/forks from the closure library github that are listed on packagist:

https://packagist.org/packages/platinumpixs/google-closure-library

https://packagist.org/packages/jupeter/composer-closure-library

It looks like the only difference is a composer.json file. I would like to see google officially list this on packagist as I'm running this in a production environment.

[Steve Hicks]

We discussed this among the team today and decided it probably doesn't make sense for us to have a presence on various non-JS package managers.  The Google PHP API Client example does not (to my mind) provide sufficient precedent, since it's actually a PHP library.

We do have an NPM package (https://www.npmjs.com/package/google-closure-library) and I believe there are bridges between Composer and NPM (e.g. https://packagist.org/packages/eloquent/composer-npm-bridge), though I haven't looked into how they work.  If you're concerned about the security implications of a third-party package, you're also free to make your own fork for Composer, which you could control.

--

---
You received this message because you are subscribed to the Google Groups "Closure Library Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to closure-library-d...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.