On the other hand, CVS seems ideal for well matured development where the project is no longer undergoing major changes.
There is one fact though, I hesitated from using CVS for a long time because I was unable to grasp the concept quickly. Though I did eventually figure it out many other developers just throw their hands up and walk away from contributing to open source projects. I got a friend who rewrote and optimized the code for reading and writing files in the id3lib C project but he just doesn't want to learn CVS to check them in. I think the SVN has potential to attract other contributors.
Perhaps the use of CVS or SVN should be based on where the specific wxcode project is in maturity. What does everyone think?
--angelo
On 4/4/06,
John Labenski <[EMAIL PROTECTED]> wrote:
> > Given that it's not possible to checkout a single file
> this is possible...
>
> > and create a diff
> > without having to get the full repository
> this is possible, too.
I only mentioned this because my one time experience with svn was not
good and from the man page I couldn't figure out how to only get the
"CVS HEAD" (or whatever they call it) version.
> > I'm completely opposed to use
> > Subversion. While a full repository might be well suited for a project
> > developer it's completely otherwise for the casual developer depriving
> > him from making just a small patch. But I don't want to stay in the way
> > for the ones who prefer Subversion for whatever reasons. I suggest that
> > any component maintainer may be able to choose if he wants to use CVS or
> > Subversion for his components.
> yes, this can be another choice... the most important thing is probably
> just to not duplicate components: i.e. a component should be in CVS or
> in SVN but not in both...
I think we have to stick with one or the other. If someone uses a few
different components from wxCode they don't want to have to mess with
getting some using CVS and the rest with SVN.
Does using SVN break the cvs browser from the SF project page? I think
that's very useful every once in a while.
Just a note, switching to SVN won't fix SF's server problems, I think
it's just bad luck that they seem to always happen to the cvs server.
----
I vote no, just because I'm lazy, fear change, and don't want to have
to learn something new. :) [also I'm not convinced that it's really
so much better or that SF supports it as well]
If people want it however, I won't complain, too much, at least.
Regards,
John Labenski
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
_______________________________________________
wxCode-users mailing list
wxCode-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxcode-users
