Updated Plugins Guide - questions and RFT

Marius Kruger amanic at gmail.com
Tue Sep 29 00:03:07 BST 2009

2009/9/28 Robert Collins <robertc at robertcollins.net>:
> On Mon, 2009-09-28 at 12:50 +1000, Ian Clatworthy wrote:
>> > I urge you to federate this data directly into the plugins in the first
>> > place: we've written approximately all the code to do this already.


>> There are at least two issues with that I know of:
>> 1. We still need a list of plugin branch URLs *somewhere* so we can
>>    fetch them to get the rest of the data.

I was thinking that you have a plugins directory with a branch for each plugin.
Because branches store their own pull location, you can just use that.
I actually use a scmproj to manage and update all my plugins from time to time.

>> 2. We have around 100 plugins and I don't have write access to most
>>    of them.
> Well, this one is fairly solvable ;P - submit patches, and pull from a
> patched branch until they are accepted ;).

i.e. make it the minimum requirement for being on the list :)

so decide how it should work, prototype it in one plugin, advertise
the new plugin 'requirement'
and after a while only let compliant plugins on the list.

<| thanks. it looks great
U| Marius
H| <><

More information about the bazaar mailing list