Re: [Pyblosxom-devel] [pyblosxom-users] 3rd party plugin repo

[Wari W. <wa...@ho...>]

Git submodules are really pointers to commits of a particular repos.
Therefore a release of a plugin would mean a specific commit at the
original site. Publishing it together with the plugins.git (instead of
submodules) would mean that all historical logs regarding to a
particular version is lost.

Anyway, there are pros and cons of both approaches, but I have a feeling
that putting it all in to the plugins.git would lead to the contrib
situation where plugins get stale after a while. At least with
pointers/submodules, one can look up the original maintainer, and
provide updates if needed instead of updating plugins.git, and you then
have to go back to the original maintainer to update their copy.

Anyway, it's all up to you what you think best, I still think the
submodule idea is great, but I guess there are others out there using
CVS or Subversion, in which case, submodules don't work for them.

On 04/12/2012 10:36, Asheesh Laroia wrote:
> On Tue, 4 Dec 2012, Akai Kistune wrote:
> 
>> Because its not just other git repos, its all over the place. Also -
>> While I'm not sure how the git submodule process would work, in any
>> case, publishing to the repo should be akin to a "release" of your
>> plugin, while the versions in people's personal repos would be the
>> development versions.
>> I hope that it will always be possible to pull a working version of a
>> 3rd party plugin from the repo.