[BUG] bzr.1 man page out of date

[John A Meinel]

James Blackwell wrote:
> On Tue, Jan 31, 2006 at 09:51:12AM -0600, John Arbash Meinel wrote:
>>>> I would probably rather the code was inside bzrlib rather than being in
>>>> tools.
>>> I can do that if you like. My thinking was that when somebody has some
>>> time we'll also have bash completion, tcsh completion, emacs completion,
>>> etc etc. That would get kind of crufty for something that often goes into
>>> site-packages.
>> I can see your point. Enough that I don't know which way is better, and
>> since your way is already done. I'll go with it. :)
> 
> Thats 1/2 of what convinced me. The other half was that convinced me was
> I also couldn't come up with any convincing reasons that we'd want to
> change the manpage after installation:
> 
> Rob said this in another post:
> 	I think it should be in bzrlib because:
> 	tools is not available after installing;
> 	plugins can add commands;
> 	-> man page generation should be available after installing.
> 
> I did consider whether or not to include plugin help and decided against
> it. If the plugin-help subsystem knows how to distinguish between user
> installed plugins and systemwide installs then I don't know how to do it.
> 
> Another consideration is the impact this could have upon distribution
> installed Bazaar-NG. I can imagine quite a bit of confusion as distros
> decide whether or not to include the builder, the results if a user runs
> the builder by hand and puts a new manpage in /usr/local/man and then
> upgrades....

Well, I think a system administrator, who has installed a couple of
site-specific commands would like to be able to easily generate a man
page which helps out the users.

John
=:->


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060204/09a2b9ba/attachment.pgp