The problem is that by working in your own area and only making file
releases of Csound 5 sources available, with no clear method of accepting
contributions from others, you in effect become the only "real" Csound 5
developer - whether this is your intention or not.

The alternatives that I can see are:

1. You are indeed the only developer who does substantial work in Csound 5,
and I move my work on Csound 5 to the Silence CVS repository in
SourceForge, which branches the Csound 5 code base.

2. You set up _another_ shared source repository (i.e. non CVS) that you,
I, and other developers can safely and conveniently use.

3. You merge your sources into Csound 5 CVS, learn to use it safely, and
work there along with myself and, I hope, other developers. I much prefer
this alternative.

Which do you prefer? Or do you have another solution?



Original Message:
-----------------
From: John ffitch jpff@cs.bath.ac.uk
Date: Sat, 13 Mar 2004 14:57:27 +0000 (GMT)
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4309] RE: Further updates


Yes; I cannot get in line with the CVS as it changed in incompatible ways 
a little while back.  I always did a "cvs update" before working on 
Csound, but after having my files deleted on cound, and then ending with a 
system which will not (and still does not) compile on csound5 I have been 
very carefull never to use CVS from this machine on which my master files 
reside -- it was a fortunate accident that I had a copy when my files were 
deleted.

I did post a day or so ago the file/directory structure I have here, and 
you replied that you had a different layout -- but I do not know in what 
way.

You posted some time ago that Csound5 was "now" generating sound files, 
while I thought it had been for a long time.  So we are very out of step.

==John ff


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

On Sat, 13 Mar 2004, gogins@pipeline.com wrote:

> The problem is that by working in your own area and only making file
> releases of Csound 5 sources available, with no clear method of accepting
> contributions from others, you in effect become the only "real" Csound 5
> developer - whether this is your intention or not.

I object very deeply to this remark.  I have been attempting to take
all the changes until doing so DESTROYED by tree.  For example I jave
just attempted to get in sync on my other main machine (cage) and it
updates, and then autoreconf fails.  So I have a choise of doing
nothing or making a working system.  Which would you choose?
> 
> The alternatives that I can see are:
> 
> 1. You are indeed the only developer who does substantial work in Csound 5,
> and I move my work on Csound 5 to the Silence CVS repository in
> SourceForge, which branches the Csound 5 code base.
> 
> 2. You set up _another_ shared source repository (i.e. non CVS) that you,
> I, and other developers can safely and conveniently use.

That is just repeating the mistakes of the past

> 
> 3. You merge your sources into Csound 5 CVS, learn to use it safely, and
> work there along with myself and, I hope, other developers. I much prefer
> this alternative.
> 

How?  Your files do not compile.  They do not even create a
./configure This is the case on 3 different machines with 3 differnt
operating systems.


> Which do you prefer? Or do you have another solution?

I would much prefer a return to a world before the configuration
tools, the need for which I have never seen.

I have managed to get almost back in step with 4.23 but I cannot even
see where the problems lie with csound5

I am not sure why it is I who has to find a solution!

==John ff

John ffitch  writes:

....
> I have managed to get almost back in step with 4.23 but I cannot even
> see where the problems lie with csound5

This is music to my ears.  Let me know if there are things I can do to
put you fully in step with csound4.  What you did for the csound
4.23f11gbs release was wonderful.

John