[Bulk] Re: bzr-plugin-info [suggest plugins at runtime]

[Gordon Tyler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 3/8/2010 4:18 PM, Marius Kruger wrote:
> On 8 March 2010 22:19, Gordon Tyler <gordon at doxxx.net> wrote:
>> I believe that a static plugin database shipped with the bzr release
>> will become rapidly out of date and less useful than it could be.
> 
> I think just having it updated at release time would cater for 90+% of
> stable plugins.
> (Thats assuming people are upgrading +- every 6 months)
> This should be sufficient for a first pass. i.e. we should not block this until
> we figure out how to magically update the list in between releases.

I honestly believe this is can be done in time for the 2.2 release or
even a 2.1.x release.

My current thinking is that it uses the same process the tool currently
uses to collect the plugin info, then packages it into a file and
uploads it to an appropriate location[1]. When a user runs the update
command, it downloads the file from the known location and unpacks it
into the user's .bazaar directory.

This is not exclusive with shipping a database with each release.

Ciao,
Gordon

1. e.g. http://bazaar.canonical.com/plugin-info-db/2.1.0/info.tar.gz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLlYypAAoJEIrPJfWinA2uuUEIAJgPRTmJmaFiiiI1rXDOn7WC
3pH4McbEub3Z+Q5QAWquQsS/Ixt6RtgCXT74iDLCTfIHeCG3BWm3HleyTPyoPceC
QpD+tnOqRltVBsPASR3vxE2/1oV+n3qGnXBvfcC+ntUh1wkq9OwTddFRwZYifTqZ
GDw784HT82veUTSAfVyxxYqw4PXVxS8OAVqQoF4diVRgBXRgS5dC5Bu/LJGUr2FW
RFnhNn5JSUmyY8DBMIxjPnRF7sv9ywliBlJKBP2fELLZVJV9rMtGF+QwVz8DJCHe
v+bsc8S1DRH7lNIPYSkvAnCrGNhNH2uC5kusgSqOBGRmGwl48wDj25G6b9xqbw4=
=IHec
-----END PGP SIGNATURE-----