[Pyrex] Source Control System

[Nicholas Bastin]

On 12 Oct , 2007, at 12:48 , Gustavo Sverzut Barbieri wrote:

> On 10/11/07, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
>> Does anyone know of a good free SCM that understands
>> the Mac properly?
>
> I don't think there is such software.

Various improvements have been made to both SVN and various mac  
development tools to better support the integration of the two.  You  
can also use command line tools to preserve resource fork data, and  
build triggers into SVN to support putting them back together when  
you get a repository.

> I don't know BBEdit, but most editos (emacs, vim...) have a way to
> specify these options in a scriptable way using a config file. For
> example, I help with various C projects, each with their own coding
> style, so I map the correct style to use based on file path. Most
> editors can also benefit from a header/footer lines with instructions,
> like # -*- coding: utf-8, mode: pyrex -*-     (emacs).

BBEdit actually understands these directives to the level that it can  
(both emacs and vim use them), so you might want to check that out,  
depending on what you're relying on the type and creator codes to do.

> As for SVN, it's an improvement, but I beg you to use a distributed
> system (git, mercurial, bazar, ...) if you want to have a read-only
> online repository, it will make easier for us to help and keep track
> of changes. (we can also use the tool, instead of keeping our patches
> in another tool like quilt, or other repository).

If you have access to a central server, there's no reason not to use  
svn.  IMO, the only reason to use a tool like git is if you don't  
have a central server with reasonable levels of access control.   
(Allow people to work on their own branches, but not merge to the  
release branches).

--
Nick