[GEM-dev] plugin development (was Re: [pix_video] error with macbook's built-in camera)

[IOhannes m zmölnig]

On 02/15/2017 04:58 PM, me.grimm wrote:
> question: could Gem plugins be developed independently of Gem main repo?
> 
> meaning right now the whole repo is forked to work on one plugin which
> seems overkill. would it make sense to split plugins from main repo, work
> on it (can this be built independent of Gem?), push, and then main repo is
> treated as submodule...
> 
> just an organizational thought which may make it easier for others to
> contribute other than dan?

well, i guess the proper way is to make the plugins become "git
submodules" of the main Gem repository rather than the other way round.

there is nothing that says that a plugin must reside in Gem/plugins/.
all the relevant headers are exported/installed, so you should be able
to start plugin development without having to fork Gem at all.


apart from that, i don't see any compelling reason what a git-submodule
approach would solve.
Gem is not a small repository, but then it is not exactly big either (45MB).

if you want your plugins to become part of Gem itself, it's probably
easier to just keep the current development model.
if you think your plugins don't fit into Gem proper, use separate
repositories.


having said that, i think that the proprietary plugins (videoPYLON,
videoHALCON, videoOptiTrack) should probably be factored out into
separate repositories.

rdsam
IOHANNES

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20170215/237c8475/attachment.sig>