pluginLibraries.append(pluginEnvironment.SharedLibrary('stdutil', Split('''
    util/cvanal.c       util/dnoise.c       util/envext.c
    util/xtrct.c        util/het_export.c   util/het_import.c
    util/hetro.c        util/lpanal.c       util/lpc_export.c
    util/lpc_import.c   util/mixer.c        util/pvanal.c
    util/pvlook.c       util/scale.c        util/sndinfo.c
    util/srconv.c
    util/std_util.c
''')))

??????? !!!!!!!

Can we please discuss changes like these BEFORE they are made?

I am maintaining a separate build system here for my platform!  Everytime
that major changes like this are made it creates a great deal more work for
me!

I had put off compiling the opcode libraries until last November because I
needed to create a separate target in a GUI build system for every single
one of them (over 60 at the time).  I spent two days (!) creating targets
and compiling and then about a week later most of them were merged.

Ten days ago I finally bit the bullet again and re-did my opcode targets to
deal with the stdopcod library.  And for the first time, I created sixteen
new targets for the utilities.  Now they have merged.  Hours more work down
the drain ...

I assume that these changes also break all of the installers for various
platforms.

I appreciate that the stdopcod library may be better in the long run -- I
may eventually come to think that about stdutil as well, although I
currently think they were better as separate libraries -- but can we at
least discuss these decisions first?

Thanks.

Anthony Kozar
anthonykozar AT sbcglobal DOT net



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Why are all the utilities merged anyway?  Rather removes the point.
==John ffitch


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I would like to know when these code reorganisations will
stop and I can spend sometime building the installer for
Feb 1?

Victor

At 10:00 26/01/2006, you wrote:
>On Thursday 26 January 2006 07:01, Anthony Kozar wrote:
>
> > Ten days ago I finally bit the bullet again and re-did my opcode targets to
> > deal with the stdopcod library.  And for the first time, I created sixteen
> > new targets for the utilities.
>
>Now you have one target, which should be simpler.
>
> > I assume that these changes also break all of the installers for various
> > platforms.
>
>No, unless an installer is very poorly written. But the installers I am
>aware of just copy all dynamic libraries, with the exception of a few
>specific ones like CsoundLib, the language interfaces, etc. as plugins.
>The list of plugin libraries does change with releases, so hardcoding it
>into an installer would not be a good idea.
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I thought we had already been round this one -- only bug fixes until
release.  Code reorganisation can disturb all the release-candidate
efforts.
  I would like a freeze from last week until 1 Feb.  Then let us
DISCUSS where we are going.

==John ffitch


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Istvan Varga wrote on 1/26/06 5:00 AM:

> Now you have one target, which should be simpler.

I like the separation from a conceptual standpoint.  But having fewer
targets to maintain manually _is_ easier from a practical standpoint.

> No, unless an installer is very poorly written. But the installers I am
> aware of just copy all dynamic libraries, with the exception of a few
> specific ones like CsoundLib, the language interfaces, etc. as plugins.
> The list of plugin libraries does change with releases, so hardcoding it
> into an installer would not be a good idea.

OK, but even if the installers were written so as to anticipate this sort of
change, there is another rather serious user issue that this merge creates.

There have been over 400 downloads of RC2 alone.  Assuming the installers do
nothing to remove old plugin libraries, every person who installed RC2 or
RC1 who now installs the final release will have the old utility plugins
sitting in their opcode directory.  Do we really want to deal with dozens of
complaints about error messages saying that the plugins fail to load because
they are duplicates?  That kind of response is not what I would call a
"smooth launch" for the much anticipated Csound 5 :)

*IF* we do move forward with the final release this way, the installers
really should remove the old utility plugins.  But that was the whole point
of the release candidates -- to work out the kinks in the installers!

Sorry, but given the timing, this just seems like a bad idea to me ...

Anthony Kozar
anthonykozar AT sbcglobal DOT net



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

So will the changes to the utilities be reverted for a Feb. 1st release?

Anthony

jpff@codemist.co.uk wrote on 1/26/06 7:28 AM:

> I thought we had already been round this one -- only bug fixes until
> release.  Code reorganisation can disturb all the release-candidate
> efforts.
> I would like a freeze from last week until 1 Feb.  Then let us
> DISCUSS where we are going.



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net