<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans Mono'; font-size:9pt; font-weight:400; font-style:normal;"><table style="-qt-table-type: root; margin-top:3px; margin-bottom:3px; margin-left:4px; margin-right:4px;"><tr><td style="border: none;">> > It would be good to make the plugin available through the standard repo,<br>
> > so everybody could update it without reinstalling qgis.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Sure. The only one important thing is to increase the version number to make the installer upgrading it (of course in the svn too).<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I don't upload it yet, because the discussion is still open and the fixed plugin is not tested well with 1.0.0 as I think. <br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> Hmm... this is a reason why I think that python plugins inside qgis<br>
> sources are not a very good idea - it brings additional maintenance<br>
> cost for developers. When someone fixes a python plugin in qgis (and<br>
> isn't owner/maintainer of the plugin), he is supposed to notify also<br>
> author so he can upload updated version so that others can make use of<br>
> it.<br>
> Am I making some sense?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Yes, it's inconvenient. However there isn't too many pythonists with svn access and we're all in contact. So I don't see it as a big problem. At least now...<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> IMO we shouldn't keep python plugins inside qgis sources (plugin<br>
> installer is the only one I would keep there) and just include some<br>
> good plugins directly to the release if it's really desired that<br>
> people get some plugins.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Or even keep them only in the main repository and provide a repo snapshots for machines without internet access.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> So in this situation I think Gary as the creator should upload new<br>
> version to repository...?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>A big advantage of the new repositories is that any admin can upload fixes without affecting the plugin ownership. So it's quite easy to do</p></td></tr></table></body></html>