[Csnd-dev] Names of binaries

Date	2018-08-09 16:21
From	John
Subject	[Csnd-dev] Names of binaries
	I did not get any response to the earlier question. At present we create/install the following binaries: First those which indicate there are part of csound: cs csanalyze csb64enc csbeats csdebugger csound winsound and a couple with names that are possibly connected to csound: scot scsort and then the problematic ones: atsa cvanal dnoise envext extract extractor het_export het_import hetro lpanal lpc_export lpc_import makecsd mixer pv_export pv_import pvanal pvlook scale sdif2ad sndinfo src_conv Some of these names are used by other programming systems, and others are rather unclearly related to audio let alone csound. I think we should rename most of these to include "cs_" as a prefix or something similar. This is of course an incompatible change for some peopes workflow. Should we do it? If so to all or some? Suggestions please.

Date	2018-08-09 20:12
From	Rory Walsh
Subject	Re: [Csnd-dev] Names of binaries
	Hi John. I was waiting for others to chime in here as I rarely use any of these tools. I'm not sure about prefixing them with a cs_ as I think it could well break a lot of scripts that people have come to rely on. It's better to hear from those who actually use these tools. Perhaps you could post to the users list to see what people there think of your proposal? On 9 August 2018 at 17:21, John <jpff@codemist.co.uk> wrote: I did not get any response to the earlier question. At present we create/install the following binaries: First those which indicate there are part of csound: cs csanalyze csb64enc csbeats csdebugger csound winsound and a couple with names that are possibly connected to csound: scot scsort and then the problematic ones: atsa cvanal dnoise envext extract extractor het_export het_import hetro lpanal lpc_export lpc_import makecsd mixer pv_export pv_import pvanal pvlook scale sdif2ad sndinfo src_conv Some of these names are used by other programming systems, and others are rather unclearly related to audio let alone csound. I think we should rename most of these to include "cs_" as a prefix or something similar. This is of course an incompatible change for some peopes workflow. Should we do it? If so to all or some? Suggestions please. ==John ffitch

Date	2018-08-10 03:33
From	luis jure
Subject	Re: [Csnd-dev] Names of binaries
	el 2018-08-09 a las 16:21 John escribió: > I did not get any response to the earlier question. Sorry I didn't respond before, I think this is an important issue. "extract" definitely conflicts with binaries from other packages. On gentoo linux, this is solved by the installation script [] by renaming "extract" to "csound_extract", but this is not ideal because it's not portable across systems. I think it would be a good idea to identify in some way all the binaries belonging to csound, for example with a prefix, as suggested. [] gentoo doesn't distribute binary packages, but rather scripts that download, configure, build and install from sources.

Date	2018-08-10 14:58
From	Felipe Sateler
Subject	Re: [Csnd-dev] Names of binaries
	On Thu, Aug 9, 2018 at 10:33 PM luis jure <ljc@internet.com.uy> wrote: el 2018-08-09 a las 16:21 John escribió: > I did not get any response to the earlier question. Sorry I didn't respond before, I think this is an important issue. "extract" definitely conflicts with binaries from other packages. On gentoo linux, this is solved by the installation script [*] by renaming "extract" to "csound_extract", but this is not ideal because it's not portable across systems. I do the same in the debian package. I think it would be a good idea to identify in some way all the binaries belonging to csound, for example with a prefix, as suggested. +1 -- Saludos, Felipe Sateler