Bug#768388: [Cs-dev] Bug#768388: csound, cs: error when trying to install together

[jpff]

I would prefer a simpe renaming, despite the pain of completions in the 
shell.  I do not think we guarantee scripts, just API and csd/orc/sco 
files.
==John

On Mon, 24 Nov 2014, Felipe Sateler wrote:

> Hi,
>
> On Mon, Nov 24, 2014 at 12:21 AM, Steven Yi <stevenyi at gmail.com> wrote:
>> I don't know how many users use cs or extract.  I guess if we change names,
>> there's a possibility we might break user's scripts or tools if they depend
>> on those names.  On the other hand, if you're doing renaming for extract and
>> no one has really complained, I suppose changing cs won't be a big issue
>> either. One thing though, either way if you rename the generated cs binary
>> or do so in the debian package, I think we should add a note to the manual
>> about the alternate names.
>
> I would prefer to not deviate from upstream as much as possible. So if
> upstream finds an alternative name, that would be the preferred
> solution for me. If upstream doesn't want to rename (which is of
> course understandable), I will probably rename to csound_cs (for
> consistency with csound_extract).
>
> The extract program should be documented as named csound_extract in
> debian and derivatives.
>
> -- 
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>