On 07-Jul-99 Brian Paul wrote:
> Questions:
> 1. Shouldn't there be a "configure" file? Or, how do I make it?
It's generally a bad idea to include the generated files (configure,
Makefile.in etc.) in the CVS tree because every time you modify one
of the source files (configure.in, Makefile.am etc.) you have to
regenerate all files and commit them to the repository.
That'd be unnecessary overhead and anyway developers are supposed to
have autoconf/automake installed.
To generate the files just run the "bootstrap" script in the
toplevel directory.
> 2. I'd like to move the COPYING and ChangeLog files into the docs/
> directory. OK?
> 3. What is the AUTHORS file for? That info is in the README file.
I was trying to make Mesa conforming to the GNU standards.
They require those files to be in the toplevel directory,
which is IMHO reasonable. I could remove the AUTHORS file, however.
I strongly recommend to use the ChangeLog file, which is very useful
in order to see what other developers have done.
Moreover, I suggest to move the contents of the docs/README file
back to README and add the reference to docs/README* to the end.
This way we'd have all important files in the toplevel directory.
What do you think?
> 4. Are you going to write documentation for all the configuration
> options?
Yep. Done.
PS: Do you want me to autoconfiscate glut, too?
PPS: I've given up working on the generic Mesa interface due to
1. lack of time
2. unifying the simple driver APIs (FX, GGI, SVGAlib) was quite easy
but it's much harder to integrate the Xmesa API than I initally thought.
Thomas Tanner -----------------------------------------
email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de)
web: http://home.pages.de/~tanner
GGI/Picasso: http://picasso.ffii.org
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
