Hi Guillaume, Guillaume Desmottes a écrit : > Le samedi 17 octobre 2009 à 14:14 +0200, Michał Sawicz a écrit : >> Dnia 2009-10-17, sob o godzinie 13:02 +0100, Guillaume Desmottes pisze: >>> Currently all the plugins are named (on launchpad and in their root >>> directory) elisa-plugin-$FOO. >>> I'm wondering if it's ok to name a new plugin moovida-plugin-$FOO >>> instead.
On Launchpad it's more than OK. Don't forget to register your project as part of https://launchpad.net/elisa-universe. We are in the process of renaming all references on LP from elisa to moovida, and that should be transparent to everyone. >>> The egg file would still be named elisa_plugin_$FOO-$VERSION.egg as >>> Moovida doesn't source moovida_plugin_*.egg files but that's an >>> implementation detail invisible to users. >>> >>> Thoughts? >> Yeah I'm doing the same thing - name the plugin moovida-plugin-x, just >> leave every elisa reference needed for the plugin to work :) > > Cool, will do that. > > Btw, should I still include the generated egg-info directly in my bzr > directory? I never really got the point to version it. It's done in Moovida's development branch for convenience: just check out the branch and run it, no need to generate the egg-info of all the plugins. Since the usual way to test an external plugin is to generate an egg anyway, there's no point in versioning the egg-info directory. You can have bzr ignore it. > thanks! > > G. Cheers, Olivier
