| You are asking for CsoundVST to be in its own package, with a release field
instead of a concatenated filename, right? And that's all? I can do that
myself, we do not need to involve John Fitch.
I must say I am mystified by the wcCsound/Csound packages. Why don't you
ask John Fitch for file release administration priviliges?
Original Message:
-----------------
From: ramsdell@mitre.org (John D. Ramsdell)
Date: 29 Dec 2003 06:38:47 -0500
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3834] csoundvst release package
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
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ . |