[Qgis-developer] PyQGIS strategy

[Maxim Dubinin]

CF> I think this very idea has been passed around a bit on the lists and
CF> irc. It would certainly be a good idea, and I for one would certainly 
CF> take advantage of it.
I'm too late as usual! Sorry for duplication ;)

CF> How was this implemented? Did you use python? Would you mind sharing
CF> your clever methods ;-)
It is so straightforward, that feel awkward to share :)
Here is the exlanation: http://gis-lab.info/qa/qgis-repo-update.html
It is all in my language, but I hope everything should be clear
from the code inserts, it involves 1) bash script and 2) python
script, nothing else. Also, note I'm not specialist at all, so there
might be problems, that I didn't know.

But it works, right now. One commit, one plugin update.

-- 
 Maxim                          mailto:sim at gis-lab.info

Вы писали 28 января 2009 г., 17:28:11:

CF> Hi Maxim,
>> Hi all,
>>
>> this question might have been already discussed, sorry if I missed it.
>>
>> First of all, the idea to have a centralized plugin storage [1] is great
>> (I was a huge fan of Arcscripts). What is not so great is that I have to re-upload
>> our plugins (so far just 1, but potentially dozens) again and again,
>> as they are developing. What makes it even more painful is that we have our own website with plugin
>> repo too, that updates on commit, nice and easy. We're quite happy
>> with our own repo and not going to abandon it anytime soon.
>>   
CF> How was this implemented? Did you use python? Would you mind sharing 
CF> your clever methods ;-)
>> So, one suggestion, please consider putting in [1] not only the plugins
>> themselves, but also parse uploaded repo.xml, so that, if authors website is up and
>> running, the person won't risk to deal with even slightly outdated
>> plugin, that I forgot to update on [1]. Also, it can be made to
>> periodically store a local copy of plugins (again
>> automatically from the websites) just in case the author's website is
>> down.
>>   


CF> Cheers,


CF> Carson