KDevelop 3 and KDE CVS Repository
Jens Dagerbo
jens.dagerbo at swipnet.se
Thu Nov 20 10:01:23 GMT 2003
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 20 November 2003 03.38, Gary Cramblitt wrote:
[snip]
> I like your approach because it separates the CVS stuff from KDevelop
> stuff without having to repeatedly figure out what to copy back and
> forth. What do others think?
I much prefer what you outline in the wiki document. I can't see any point (or
need) for not developing with KDevelop in your local copy of the CVS
repository. What's the reason for wanting this? It seems to me to be asking
for trouble. :)
When you, after developing with a KDevelop generated project locally, get to
put the project into CVS - add what you think you should to CVS and then
check it out again to a _new location_ on your disk.
Then use this new location for continued development.
This way you know that your project structure is exactly the same as what
other potential project members will have when they check it out.
(Btw, I haven't been able to register with the wiki yet. There are some minor
details I'd like to add, but it appears the "registration code" feature is
busted..)
// teatime
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/vJD36meJzsUuplQRAhcrAJ0fSwXvUdZRKEiHSuBtDHUEcYP7RACfU/4i
IKtBnCJJuHZf8DnazKu94i0=
=b4TI
-----END PGP SIGNATURE-----
-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«
More information about the KDevelop
mailing list