Hi Paul, I just noticed my mistake, thanks to your analogy. I was thought that https://github.com/apache/couchdb-examples/tree/master/my-first-couchdb-plugin is a part of couchdb-couch-plugin, but didn't check that.
Anyway, if these both are could coexists with the registry that would be cool. -- ,,,^..^,,, On Wed, Mar 18, 2015 at 7:00 PM, Paul Davis <[email protected]> wrote: > Hiya, > > The couchdb-couch-plugins repository is for downloading and installing > plugins from a registry. I know Jan was working on it at one point as a > proof of concept type thing but not sure where its at today. > > Plugerl on the other hand is for defining callbacks that can be used by > plugins. > > The two are orthogonal. Code installed via couchdb-couch-plugins could have > hooks for the callbacks defined by our plugerl modules. Or not if they > don't need to. > > A Python analogy that comes to mind, couchdb-couch-plugins is kinda like > pip, plugerl is like entry_points. > > HTH, > Paul > > On Mon, Mar 16, 2015 at 1:18 PM, Alexander Shorin <[email protected]> wrote: > >> Hi Ilya, >> >> That's good news, but how this all will be related to existed >> https://github.com/apache/couchdb-couch-plugins ? >> -- >> ,,,^..^,,, >> >> >> On Mon, Mar 16, 2015 at 9:12 PM, Ilya Khlopotov <[email protected]> wrote: >> > >> > Hi, >> > >> > I would welcome any feedback on using proposed plugerl applications to >> > implement vendor specific hooks >> > >> > https://issues.apache.org/jira/browse/COUCHDB-2585 >> > https://github.com/apache/couchdb-global-changes/pull/4 >> > https://github.com/iilyak/plugerl >> > >> > What are the next steps I need to take besides fixing issues discovered >> by >> > reviewers? >> > >> > BR, >> > ILYA >>
