On Tue, Jul 19, 2016 at 10:47 AM, Alexander Gerasiov <g...@cs.msu.su> wrote:
> Every plugin is just a small parser class which is called from
> ofxstatement, parses input file and pass data back to main app. These
> plugins are developed independently by various people who publish them
> in separate repositories (mostly on github).

The high point I picked up here is that each plugin has it's own
lifecycle, controlled by independent developers.

> I decided to package ofxstatement as separate package, but put all
> plugins in one package oxfstatement-plugins.
> I'm not skilled in distributing python apps and packaging python
> apps into .deb, so I'd like to get some review and feedback from the
> community before upload to archive.

Grouping the plugins like this seems odd to me, because of the
independent lifecycles.  Perhaps something to consider is to create
separate debian packages for each (with names like
ofxstatement-plugin-abcdef), and maybe a convenience meta-package that
depends on some set of the plugin packages (ofxstatement-plugins).

I'm not sure whether the debian policies address this.  Hopefully
someone more knowledgable can comment on that.


Fred L. Drake, Jr.    <fred at fdrake.net>
"A storm broke loose in my mind."  --Albert Einstein

Reply via email to