In my view, maintaining a separate personal repository in which active
development is done along with a public repository is not only bad software
engineering practice, but could easily be perceived as a discourtesy by
other Csound developers -- even though you have advised us of the situation
all along -- because when somebody wants to work on the code, they
naturally go ahead and get it from CVS. There's an obvious risk of work
being lost, or of developers being forced to fix the same bugs over and
over.

I do understand you've had problems with CVS eating your work. I've
occasionally had similar problems myself. But I don't find it necessary to
develop in a separate tree. Instead, I just back up my local directories
from time to time -- copy them bodily to a CD-ROM -- and develop in the CVS
tree anyway. Why can't you do that?

One might speculate that you feel a need for more supervision of changes to
the Csound code. If that's the case, why don't you just ask people to
submit commits for your approval, the way the SuperCollider administrators
do? Or you can even go so far as to set up Csound CVS for reserved
checkouts, then checkout everything yourself. People would then email
changes to you and you would commit them (and check out the files again).
But the repository would still have the most up to date code.

It's also possible to track who is editing what. You could use this to keep
an eye on developments.

Original Message:
-----------------
From:  jpff@codemist.co.uk
Date: Mon,  9 Aug 2004 10:07:26 +0100
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:5155] Re: 4.23f12 code discrepancy?


Possibly not.  I have had great problems with the csound repository
and so attempts to keep up to date may fail.  I have a parallel
csound4 directory which does compile and so it is possible that I
never copied it back.
==John ffitch


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

"gogins@pipeline.com"  writes:

> I do understand you've had problems with CVS eating your work. ...

Please note that Csound 4 is just being maintained, and is not under
active development.  As a result, it has been a long time since a file
has been removed, the only operation that has the potential of causing
CVS to eat someone's work.  Given the stability of Csound 4, I expect
this operation is unlikely to be performed anytime soon.

Let me offer further comfort to those using the Csound 4 repository by
pledging once again to include "cvs up -d" in the subject of a message
to this list anytime I remove a file so that one knows to make a
private back up.  Let me repeat, I foresee no reason to apply this
operation.

Finally, I have been carefully tagging consistent collections of the
files in the Csound 4 repository making it easy to recreate previous
versions.  In summary, the csound module in the Csound repository is a
safe place to store and share your work.

John

Well, the simple fact is that the csound files failed to build
cleanly, so I built the release on a working tree.  As was said there
is no development in that tree and only bug fixes.  I judged it better
to fix bugs than not.  I would rather spend my time on the new.
==John ff

jpff@codemist.co.uk writes:

> Well, the simple fact is that the csound files failed to build
> cleanly, ...

Please send me build failure bug reports.  I checked out a fresh copy
of the csound module from the CVS repository.  On Redhat Linux, I
built Csound from its sources following the instructions in the README
for the case in which there is no configure script available, in other
words, when one is not using the GNU Build System.  I changed my
directory to csound, copied Makefile.lnx to Makefile, and edited it to
omit the -DTCLTK from DEFINES, and -ltcl and -ltk from the link
command, and experienced no build problems.  John, your makefiles work
fine for me.  Solid as ever.

John

the make process is totally unrelated to anything I understand so I am
nor sure what is happening.  I maintain a simple working makefile
elsewhere.

...
Making all in doc
make[1]: Entering directory `/home/jpff/Sourceforge/csound/doc'
restore=: && \
backupdir=".am$$" && \
am__cwd=`pwd` && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
for f in csoundgbs.info csoundgbs.info-[0-9] csoundgbs.info-[0-9][0-9] csoundgbs.i[0-9] csoundgbs.i[0-9][0-9]; do \
  if test -f $f; then \
    mv $f $backupdir; \
    restore=mv; \
  fi; \
done; \
cd "$am__cwd"; \
if /bin/sh /home/jpff/Sourceforge/csound/missing --run makeinfo   -I . \
 -o csoundgbs.info csoundgbs.texi; \
then \
  rc=0; \
  cd .; \
else \
  rc=$?; \
  cd . && \
  $restore $backupdir/* `echo "./csoundgbs.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; \
exit $rc
csoundgbs.texi:9: Unknown command `copying'.
csoundgbs.texi:22: Unmatched `@end'.
csoundgbs.texi:53: Unknown command `insertcopying'.
makeinfo: Removing output file `csoundgbs.info' due to errors; use --force to preserve.
make[1]: *** [csoundgbs.info] Error 1
make[1]: Leaving directory `/home/jpff/Sourceforge/csound/doc'
make: *** [all-recursive] Error 1

==John ffitch

jpff@codemist.co.uk writes:

> the make process is totally unrelated to anything I understand so I
> am nor sure what is happening.  I maintain a simple working makefile
> elsewhere.

John f.,

I was expecting you to use and maintain the makefiles in the csound
directory.  These makefiles are the ones you wrote, modified so as to
make use of the new directory structure I introduced last November.
The Linux one works appears to work as you intended it to as long as
one removes the TCL/TK references.

In any event, your message says to me that the GNU Build System is
working well for you.  It appears from your note that everything build
with the exception of the doc directory, which is built last.  You
should be able to do a "make install" now, and install everything but
the documentation.  Or you should be able to run binaries from the
place in the source tree in which they are created.  In particular,
try:

$ csound/csound

and you should get Csound's help message.

This is all very cool!  Did you update your Linux system or something?
I think it's great your making use of the GNU Build System instead of
the makefiles you wrote.

As for the documentation problem, this is a know issue.  I used a
newish feature of InfoTeX that formats the copyright statement
properly.  When I build a distribution, I use a new version to
texinfo, and the distribution includes the output.  As a result,
texinfo is not used when building from the sources in a distribution,
and the build can be performed on a platform with an old version of
texinfo.  All this is long way of saying just ignore the error.

John

> ...
> Making all in doc
> make[1]: Entering directory `/home/jpff/Sourceforge/csound/doc'
> restore=: && \
> backupdir=".am$$" && \
> am__cwd=`pwd` && cd . && \
> rm -rf $backupdir && mkdir $backupdir && \
> for f in csoundgbs.info csoundgbs.info-[0-9] csoundgbs.info-[0-9][0-9] csoundgbs.i[0-9] csoundgbs.i[0-9][0-9]; do \
>   if test -f $f; then \
>     mv $f $backupdir; \
>     restore=mv; \
>   fi; \
> done; \
> cd "$am__cwd"; \
> if /bin/sh /home/jpff/Sourceforge/csound/missing --run makeinfo   -I . \
>  -o csoundgbs.info csoundgbs.texi; \
> then \
>   rc=0; \
>   cd .; \
> else \
>   rc=$?; \
>   cd . && \
>   $restore $backupdir/* `echo "./csoundgbs.info" | sed 's|[^/]*$||'`; \
> fi; \
> rm -rf $backupdir; \
> exit $rc
> csoundgbs.texi:9: Unknown command `copying'.
> csoundgbs.texi:22: Unmatched `@end'.
> csoundgbs.texi:53: Unknown command `insertcopying'.
> makeinfo: Removing output file `csoundgbs.info' due to errors; use --force to preserve.
> make[1]: *** [csoundgbs.info] Error 1
> make[1]: Leaving directory `/home/jpff/Sourceforge/csound/doc'
> make: *** [all-recursive] Error 1
> 
> ==John ffitch

The Makefile I used got changed to something I really do not
understand; but luckily there is no development on csound4.  Naturally
I do have my own Makefile elsewhere, and Windows project files, so I
can do things.  If the make fails then it fails; messes scripts and
understanding of what it does next.
==John ffitch