Which just proves my point, because that's exactly what I did
without an SCC package! Would I like to avoid part of my manual
process by using such a package... sure. But for all the questions
and wranglings I have seen over the use of these and the
instructions of how to install and then use, I'm not sure which is
going to be the least work (I could even automate my processes
further without an SCC, which I suppose was the start of those
anyway). Even reading the Darcs manual last night filled me with
dread, although I like the approach, but still it lacks integration.
I can't speak to Darcs, but for CVS/Eclipse (and I just did this
process, so I know it's all that's required):
On Server:
1) install a relatively recent (i think 1.11 is enough?) cvs binary
if you don't have one already
2) "mkdir /Path/To/Repository/Folder"
3) "cvs -d /Path/To/Repository/Folder init"
4) enable ssh
On Client:
1) in eclipse, open CVS perspective
2) add repository: host = yourserver.com, repository = /Path/To/
Repository/Folder, connection type = extssh, username = youruser,
password = yourpw
and you're done. You can now Team=>Share a project to do an initial
checkin, File=>Import=>From CVS a project that's already there, or
Team=>Synchronize an existing project to see incoming and outgoing
changes. The integration is really nice. If you're using Xcode,
you're both on your own and a masochist :)
Just to play devil's advocate a bit more, I'd still like to see
such functionality built into a development environment – a system
editor, rather than the primitive text editor-based environments of
today. The problem I have with SCC packages is they are yet another
thing I have to learn separate from Xcode and others.
For what it's worth, Eclipse DOES have a local repository that
automatically tracks all your changes and has most of the core
revision control goodness, but it obviously doesn't cut it for beyond
a single user.
On the other hand, the advantage to a separate SCC system is that
people can use their environment of choice like Xcode or Eclipse or
other. I think we are just patching up primitive tools with more
primitive tools.
Well, sure, but if patching primitive tools with primitive tools
makes your life easier, then so be it. If it doesn't for you, that's
cool, too ... but I think you're wrong ;)
ms _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
