Well, I don't have authority to create packages either! - I assumed because
I could create releases, I could create packages.

The CsoundVST release also contains all Csound sources and a Microsoft
build system, as well as a Dev-C++ build system. This is not optimal. I
think we both agree that it's best to require that the csound package be
installed, and link with that, for our projects.

John Fitch - would you please create a csoundvst package and move the
csoundvst-2003-12-28 release into it? Or give me the privileges to create
packages?


Original Message:
-----------------
From:  ramsdell@mitre.org (John D. Ramsdell)
Date: 29 Dec 2003 09:44:49 -0500
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3837] RE: csoundvst release package


"gogins@pipeline.com"  writes:

> 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?

I have file release privileges, but I cannot create packages.  This is
why I cannot make a csoundvst package.  Besides, I didn't want to
change things without you being in the loop.

And yes, the wxcsound package is strange in that its current release
also contains a csound release.  That is what I am attempting to fix.

John


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

"gogins@pipeline.com"  writes:

> John Fitch - would you please create a csoundvst package and move
> the csoundvst-2003-12-28 release into it? Or give me the privileges
> to create packages?

I suggest you ask him only to create the csoundvst package, and you do
the move so it ends up just as you want it.

John