Re: gEDA-dev: Considering git

[Dan McMahill <dan-at-NOSPAMmcmahill_dot_net>]

Svenn Are Bjerkem wrote:
> On 6/8/07, Stephen Williams <steve@icarus.com> wrote:
> 
>> And gEDA going to git adds some degree of peer pressure, too:-)
>>
>> The real question for me, therefore, is "why git instead of CVS?"
>> For me, the off-line support is the killer app.
> 
> How is git as an SCM tool for HDL? Can Verilog/VHDL projects with many
> developers/modules be nicely kept up to date with git?

since I view HDL as any other text source file, I'd imagine so.

> Could git also handle Cadence cdb data?

I think the 3 things it needs are

1) atomic commits which I believe git has.  This is needed since some 
cadence files must stay in sync with others.

2) capability to deal with binary files.  I'd be suprised if git 
doesn't, but you'd need to make sure you can check in a binary file and 
not have git try to expand keywords or do merges.

3) this is the big one.  You probably want to be able to grab a write 
lock on cdb files.  Since you can do diffs or merges (since cdb is 
binary) I think a locking work style is the only one that makes sense 
for the cdb part.  Also you'd like to specify locking or shared modes on 
a file or directory basis, not on a repository basis.  That way for HDL 
you can have multiple edits at once and do merges but still get correct 
behaviour for cdb data.

> I am just asking to find an alternative to clearcase and designsync.

well, don't forget you'd probably want to tie into the gdm interface in 
cadence and get everything working in the library manager.  Thats 
probably not that much fun.



_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev