bzr-update-copyright

[Neil Martinsen-Burrell]

On 2010-01-11 12:34 , John Arbash Meinel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Martin Pool wrote:
>> 2010/1/9 John Arbash Meinel<john at arbash-meinel.com>:
>>> So having thought about this a bit, I realized there is a *really* good
>>> use case for this. I went even one step further and the plugin now
>>> installs a 'start_commit' hook. Which means that if you have the plugin
>>> installed, and set "auto_update_copyright=True" in your configuration,
>>> every time you commit I'll scan for modified files, and then check to
>>> make sure that their copyright headers are correct.
>>>
>>> IOW, it will permanently keep your Copyright headers in sync with the
>>> data that Bazaar has for the file. (For files which you modify.)
>>>
>>> This is a neat enough feature that I'm turning bzr-update-copyright into
>>> its own project.
>>>
>>>   lp:bzr-update-copyright
>>
>> That's great.  Can you add it to the plugin guide too?
>
> I would be happy to. If I understood how to do so.
>
> I was able to track down:
> lp:~ian-clatworthy/%2Bjunk/bzr-plugins-guide/
>
> Upon checking it out, it then has a couple of .py scripts that seem to
> be relevant for rebuilding. I'm not 100% sure what files are
> autogenerated and what is not. However, both "add-guide-links.py" and
> "mkregistry.py" require an external data file "wiki-data-2.txt" and
> "wiki-data.txt", neither of which are present in the branch.

1. Checkout lp:bzr-alldocs
2. Add plugin to plugins-registry.ini
3. from plugin/en folder run ../../scripts/document-plugin.py 
update-copyright
4. bzr add update-copyright-plugin.txt
5. Add update-copyright-plugin to the appropriate section in 
plugins/en/index.txt

This is the description in the relevant section of the Plugin Guide 
itself, but it hasn't migrated into doc/developers yet.

-Neil