i dunno if this is relevfant or not, but yes, I keep "my copy" of the sources on a linux machine and rely on scripts to zap them over to Windows when I need to compile&test there -- ditto for irix; for linux I actually just download the source tarball and compile like anyone else would.
One thing I'm confused about is how to deal with my one directory that contains sources, compiled objects, and all my related scripts for moving things around, testing then, etc. So far I haven't taken the time to organize them in a way that would support moving the sources to a repository.
Another source of anxiety for me is that I don't know (and would have to learn) what a good policy would be for maintaining reliability when multiple people are checking code in and out. I believe the best way is to have an exhaustive test suite, but building that would take a huge chunk of time!
cheers Miller
On Fri, Apr 26, 2002 at 04:52:52PM +0100, david casal wrote:
On Fri, 26 Apr 2002, [X-UNKNOWN] günter geiger wrote:
Looks pretty interesting. From reading the description, what I understand is that it forces people to do the source managment in a structured way. This is one thing that programmers using CVS have to learn first.
That's the case AFAIK.
As a big drawback I consider the fact that they say their Windows support is weak, and as pd externals are windows too..
Indeed. Exclusion is not really the way forward. Though actually (someone correct me here if I'm wrong), development of PD's main code is never done on a windoze platform, just tested on one. It would still affect externals development, though, you're right...
Another point contra aegis, we have to run our own server and can't use sourceforge for aegis.
I would strongly volunteer to run Aegis on UEA labs, but I see your point.
Oh well.
DC
david casal --0+
d.casal@uea.ac.uk --9+
www.ariada.uea.ac.uk/~dcasal --)+