I think my point would be closer to not allowing a package on-board without adaqate instruction on what it was and how to use it.

Where is the value of providing a widget to a customer without giving them a clue as to what the widget is or what to do with it.

Mac <almost nap time> McCaskie

Kent West wrote:

Mac McCaskie wrote:

-Found packages with no available documentation


This is a peeve of mine. I was under the impression that nothing got into the archives without a man page, even if the man page said nothing more than "sorry, there's no information here".


Perhaps that rule only applies to the "main" archive or something similar. Or perhaps I just dreamed I read it once somewhere.

At any rate, I think it'd be a good thing to enforce, that no package be allowed into the main archives without some sort of man page, even if it just says "I'm too lazy to write a man page, so you'll have to scour the source" or something similar.

If I'm just lowering the S/N (signal-to-noise) ratio here, my apologies.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Reply via email to