KDE CVS Commit Policy (3rd version)

[David Faure]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 12 April 2003 02:07, Cornelius Schumacher wrote:
> <p><b><a name="18">Don't add generated files to the repository.</a></b></p>
>  
>  <p>Files generated at build time like moc files, the files generated from 
ui
>  files or Makefiles shouldn't be checked into the repository because this is
>  redundant information and might cause conflicts. Only real source file
>  should be in CVS.</p>

I think this is a bit simplistic. We do have some generated files in CVS, and 
there's a reason for that. 

I would at least add "if the tools for rebuilding the generated files are not 
an unusual requirement". If you write a e.g. ruby script to generate a cpp 
file, I'd really prefer the generated file to be in CVS (as well as the 
script of course), instead of forcing everyone to have ruby installed. A more 
tricky case is e.g. perl - do we require it nowadays? Hmm I guess libkabc 
does.

I guess the other reason is that telling automake how to generate files before 
compiling isn't obvious to everyone - when there's no direct support from the
build system, like we have for moc and ui. Well, if coolo confirms that
kdelibs/kabc/Makefile.am does it the right way, I could add that to the 
Makefile.am howto (see sig).

- -- 
David FAURE, faure at kde.org, sponsored by TrollTech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
How to write a Makefile.am for KDE/Qt code:
http://developer.kde.org/documentation/other/makefile_am_howto.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+l72Z72KcVAmwbhARAtNoAJ95TcQGOoy05t2hu1uLSCoMD1znegCbBAjr
PKGgRq7L+kowK/Y8ACKFOzw=
=W+R2
-----END PGP SIGNATURE-----