Re: Making GNOME CVS more usable

["Timur I. Bakeyev" <gnome listserv bat ru>]

I do prefer to have several small files with  explicit content rather than
one huge all-in-one README file...

For example I'd like to see DEPENDENCIES file in each project directory, so,
compiling from scratch I should know, what else I do need. At the moment
it's mostly multiple run-and-test process untill all the dependecies are
satisfied...

So, I do like Matthias proposition and would like to see all the documentation
files in ech project directory. 


On Tue, Mar 27, 2001 at 08:54:25PM +0930, Not Zed wrote:
> I would have thought a decently complete README file would cover this
> enough?
> 
> On 26 Mar 2001 15:14:02 +0200, Matthias Warkus wrote:
> > OK...
> > 
> > This was proposed a long time ago already, but I thought that we could
> > maybe discuss this again.
> > 
> > Every module on GNOME CVS should contain a file, called maybe
> > "SYNOPSIS" or such, describing in a short paragraph just what that
> > module is and does. I propose also adding a file "REQUIRES",
> > describing all other CVS modules and/or external libraries the module
> > requires.
> > 
> > Scripts could use these files to create a module catalog and even a
> > dependency tree.
> > 
> > I would actually volunteer to create SYNOPSIS and REQUIRES files
> > everywhere they do not exist. I'm sure we can find someone to write
> > the scripts, too.
> > 
> > What do you think?
> > 
> > mawa

_______________________________________________
gnome-hackers mailing list
gnome-hackers gnome org
http://mail.gnome.org/mailman/listinfo/gnome-hackers