OK, --place it will be.

Original Message:
-----------------
From:  ramsdell@mitre.org (John D. Ramsdell)
Date: 28 Dec 2003 22:16:34 -0500
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3830] Re: csound5


"gogins@pipeline.com"  writes:

> John Fitch, and other Csound developers, please let me know if you
> agree...

I agree with one minor amendment.  As I said before, please place the
Csound API header file or files in csound5/include/csound, not
csound5/include.  This makes the --place option in csound-config work,
so one can build add-on packages without having csound installed.

Michael, you'll be happy to know I've made a start on flCsound.  There
is a new CVS module by that name.

John


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

Michael,

Please ask John to create a csoundvst release package on SourceForge,
and perform file releases of CsoundVST within that package.  Use the
release field to identify the version of the release--not the package
name concatenated with the version identifier.

I ask for this change so that the current stable csound source tarball
and RPM can be released in the csound package as version 4.23.1.
Currently, it is released in the wxcsound package and version 1.0.2,
which probably mystifies visitors to the site.

Note that there need not be a one-to-one correspondence between
packages and CVS modules, so even though CsoundVST sources are stored
in the csound module, there is no requirement that CsoundVST be
released in the csound package.

John