Johnny Hughes wrote:
The other problem with a single readme file is that it can't be contributed by more than one person, so if a new RPM comes along, the person with the master readme has to edit and upload it. If the readme was per RPM or set of RPMs then that would not be a problem. You could also include info like who built the RPM and how to contact them etc.
I was going to have a docs directory, but decided to put it in one file instead. (I figured it would be easier if it was in the main directory and in one file). I am not tied to that concept, so if lots of people think separate files are better, we can do that.
Perhaps we could even go to a Wiki, with a page per package ? This sounds like the ideal kind of scenario for a Wiki.
The issue being, are we really going to have so many packages to warrant the added admin overhead of a Wiki ?
- KB