use official/stable releases of external libraries [#1054950]

It appears that this module is designed only to work with hacked versions of glip. Also, glip has no official release as of yet.

In the spirit of using the libraries module at all, this module should use the version of glip which a user would download and install into his libraries path (or into his system PHP include search path). He shouldn't need to be directed to a special fork.

So, this is a request that Upliner and halstead work with patrikf to integrate their changes to glip into the official glip tree, and that they also ask glip's maintainer to make an official release of glip. Regardless of whether or not this makes sense at the moment, it should be done before git_deploy is considered stable: an application may only be considered stable if all of its dependencies are first stable.

Comments

Comment #1

halstead commented 8 February 2011 at 21:40

I'm looking into this.

Comment #2

halstead commented 8 February 2011 at 22:44

I've contacted Patrick to see how he feels about creating a project page for glip at code.google.com or sf.net where we could host a more official download of glip.

Apachesolr, which is deployed on drupal.org, depends on SVN revision 22 of solr-php-client from code.google.com so I think this will be official enough to count.

In the meantime I've tagged a 1.0 release on github and updated the README.txt to point to the released version.

Comment #3

ohnobinki commented 8 February 2011 at 23:21

I've contacted Patrick to see how he feels about creating a project page for glip at code.google.com or sf.net where we could host a more official download of glip.

Oh, I'm not saying you or Patrik have to do anything as drastic as that! Sorry if I sounded so harsh ;-).

What I'm looking for is for Patrik to at least use github's tag -> download feature, to have at least a reference “stable” release of glip for people to use. Thanks for your quick response and work on this; tagging a 1.0 release is at least a start :-).