David Teran, david.teran@..., wrote:
>> I concur subversion is less evil than cvs. I would not call it 'great',
>Great or not, i like to work with it because it works much better ;-)
I can get on board with 'works much better'. (grin)
>> This statement instills great fear for me. I have to load a runtime
>> into EOModeler into order for it to play nice with svn?
>Yes, but this is not new: there were times where eomodeler was unable
>to work with cvs for the same reason and the only solution was to load
>a eomodeler bundle. Its just about deleting the CVS directories and now
>the .svn directory.
Where is this hack located. Maybe if I looked at the code I wouldn't be
>> I rely extensively on SourceForge's CVSWeb/ViewCVS abilities. Am I
>> correct that svn offers something comparable?
>Do not know at all.
I know svn relies on http for its transport -- I just don't know if it
offers a pretty HTML GUI as well.
>> Finally, have you considered dropping the entire bottleneck-based
>> that cvs and svn use, and use something fully distributed like arch? In
>> particular, tla? While I have personally dismissed tla as unworkable
>> myself, it may fit with this particular project's goals.
>I do not know either arch or tla. Will have a look at it.
Tom Lord's arch (tla, arch coded in C):
Tom Lord's "diagnosing svn":
So, tla is the best thing I know of. That said, I can't fully recommend
its use for Wonder:
* I haven't used it in production.
* The current inventory tagging methodology is fundamentally broken (but
* I disagree with the license (which is one of the primary reasons I
haven't 'fixed' the above flaw).
* It has a unix-based worldview. That means it doesn't understand things
like creator types, or resource forks. This doesn't hurt Wonder too much,
and should be fixable as well, however:
* The driving personality is inhospitable to others.
* Same lack of GUI tool support (which two friends and myself where going
to solve until we ran headlong into license incompatibility issues).
* May also need the EOModeler bundle hack as well (I'm unsure at this
point -- I could see another technique which kills the need)
>If i remember correctly Anjo mentioned some commandline shells that are
>able to emulate a cvs commandline tool but i do not know if for example
>BBEdit just wraps the cvs binary or if it implements the protocol
To my knowledge, BBEdit just calls cvs itself.
>It seems there are more open questions than i thougt... i am only using
>the commandline when i work with cvs and therefore the transition to
>svn was quite easy for me. If someone uses GUI tools for cvs it might
>be much more complicated. I also wonder if our on anyone infrastructure
>(mentioned in a previous mail) is reliable enough. But generally i
>would really like to 'switch'.
I think a poll is in order here. Committers, do you use the cvs
command-line tool? Or do you use a GUI tool?
Jonathan 'Wolf' Rentzsch http://rentzsch.com
Red Shed Software http://redshed.net (847) 584-7465
PGP: b2af 1a09 f881 ebde c9d6 c4d2 c04f a3c0 3ec5 d5f2
"better" necessarily means "different"