Comment 1 for bug 731102

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 731102] [NEW] rename plugin to push_and_update to allow it to just work with bazaar plugin system

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

On 3/8/2011 8:53 AM, Xavi wrote:
> Public bug reported:
>
> Hi all:
>
> I'm new to install plugins in bazaar, and yours was my first attempt. I
> followed instructions on http://doc.bazaar.canonical.com/plugins/en
> /plugin-installation.html
>
> (i.e. branched from lp in my home .bazaar/plugins/ directory).
> However, when I requested bazaar to display the installed plugins, I got this message regarding your plugin:
>
> ------------------------------------------------------------
> invalid syntax (<string>, line 1)
> Unable to load 'bzr-push-and-update' in '/home/xavi/.bazaar/plugins' as a plugin because the file path isn't a valid module name; try renaming it to 'push_and_update'.
> ------------------------------------------------------------
>
> I renamed the whole folder to push_and_update, and bzr plugins then showed your plugin as another of the installed plugins.
> So maybe renaming the plugin might be worth to reduce the number of steps needed for newbies for the plugin to work?
> Just a hint, and thanks for this plugin! (a pity that bazaar can't update a working tree over sftp)

 status: wontfix

Unfortunately, I'm following the standard naming scheme. We label all
plugins "bzr-XXX" so that it isn't confusing on Launchpad. Eg 'bzr-git'
is the plugin for 'git' interoperability. Since we are already naming it
'bzr-XXX', then you have to specify a target name anyway. We added the
code in the importer to help people realize that they need to rename it
to conform to python standards.

If this plugin were packaged, the packaging would make sure it was put
with the correct name. It is only an issue for people checking out directly.

John
=:->

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

iEYEARECAAYFAk116s4ACgkQJdeBCYSNAAN5xACfbulVqvfZvKe976YRuxrMhWzQ
alUAnRhWOR4YCsoJP+JehkyD1MQXRJZX
=qIFp
-----END PGP SIGNATURE-----