[Kde-accessibility] Makefiles in kdeaccessibility

[Olaf Jan Schmidt]

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

[Sarang Lakare]
> Yes. And I also suggest that all the projects and the module itself
> should each have a kdevelop project file (w/o built-in Makefile
> support) so that new developers wanting to join can simply click on the
> project file and start working.

The idea is good, but this would force all people possibly adding or=20
removing files to use KDevelop, for otherwise they cannot update the=20
kdevelop file. And is it really worth to keep updating the kdevelop file=20
if we don't know of any new developers who are interested in using a=20
particular version of KDevelop?

Also I am not sure whether it would be against the KDE CVS policies to ad=
d=20
project files to the repository - especially since I heard rumours that=20
direct CVS support is thought of for Kdevelop 3 ("Gideon"), and Kdevelop=20
3 uses different project files than KDevelop 2.

Olaf.

- --=20
Olaf Jan Schmidt, KDE Accessibility Project
KDEAP co-maintainer, maintainer of http://accessibility.kde.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj4wV4oACgkQoLYC8AehV8dR7QCfbW33oZcvjrjqUG/vEx2eJmIb
8vQAn04IBZRx+52rGejm9odY//dkxVnS
=3DjHqf
-----END PGP SIGNATURE-----