Hi Steven,

I noticed there is no download version yet at that location , but there is a
download option on the overview page, so I used that.

Richard



--
View this message in context: http://csound.1045644.n5.nabble.com/CSPM-Server-tp5717776p5717778.html
Sent from the Csound - General mailing list archive at Nabble.com.

Found it under the tags section, as you mentioned in your previous post.

Richard



--
View this message in context: http://csound.1045644.n5.nabble.com/CSPM-Server-tp5717776p5717779.html
Sent from the Csound - General mailing list archive at Nabble.com.

Hi Steven,

Thanks for the work on this. I think it's a great idea.

How do you think architecture should be handled? (and compatibilty
with Csound versions?)

Also, I think documentation should be installed alongside the package,
and then somehow be available with the manual, or at least to
frontends which display documentation. Any thoughts on how this should
be handled?

Cheers,
Andrés


On Sat, Nov 10, 2012 at 4:54 AM, Steven Yi  wrote:
> Hi Richard,
>
> Yes, I'll work on packaging it properly for next release, as well as will
> update the cspm-server page to have links to downloading, documentation for
> using cspm, etc.
>
> Thanks!
> steven
>
>
>
> On Sat, Nov 10, 2012 at 10:50 AM, zappfinger  wrote:
>>
>> Found it under the tags section, as you mentioned in your previous post.
>>
>> Richard
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/CSPM-Server-tp5717776p5717779.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>

Hi Steven,

I'm hoping for seamless integration into front-ends, so that when a
package is installed, frontends will have some way of knowing about
the new opcodes and be able to display their documentation. It just
needs to be standardized somehow, and maybe registering the opcodes
and documentation directories in an easily parsable way.

Cheers,
Andrés

On Sun, Nov 11, 2012 at 6:59 AM, Steven Yi  wrote:
> Hi Andres,
>
> Architecture should not be an issue at this point as the packages are not
> building anything.  I think that would be important for a next step, to
> allow building C opcode libraries.  In that case, I think we could do it two
> ways: the package builder provides a build script, or we do a default build
> system in cspm.
>
> For Csound version compatibility, we could add a csound-version: field. We
> could do package variants then, something like: myOpcode-1.0@cs5.tar.bz2,
> myOpcode-1.0@cs6.tar.bz2.
>
> For documentation, that one I'm not sure. I think like packages.cspm, it
> should be an enforced convention.  My best guess at this point is that we
> use "package/docs" as a folder for documentation, with an index.html be the
> default starting point within the docs folder.  Packagers could then decide
> to add as much as they want to the docs (images, other html, etc.).  I had
> the thought to have "cspm init" create the docs folder and a simple HTML
> file to help make the process simpler.  Tools that want to look for other
> documentation could search that folder and if pdfs are found it could offer
> that possibility too.  I think the package/docs/index.html  should be
> sufficient though for tools, and users can search the folder if they want to
> see if other things are packaged there.
>
> Thanks!
> steven
>
>
> On Sat, Nov 10, 2012 at 10:06 PM, Andres Cabrera 
> wrote:
>>
>> Hi Steven,
>>
>> Thanks for the work on this. I think it's a great idea.
>>
>> How do you think architecture should be handled? (and compatibilty
>> with Csound versions?)
>>
>> Also, I think documentation should be installed alongside the package,
>> and then somehow be available with the manual, or at least to
>> frontends which display documentation. Any thoughts on how this should
>> be handled?
>>
>> Cheers,
>> Andrés
>>
>>
>> On Sat, Nov 10, 2012 at 4:54 AM, Steven Yi  wrote:
>> > Hi Richard,
>> >
>> > Yes, I'll work on packaging it properly for next release, as well as
>> > will
>> > update the cspm-server page to have links to downloading, documentation
>> > for
>> > using cspm, etc.
>> >
>> > Thanks!
>> > steven
>> >
>> >
>> >
>> > On Sat, Nov 10, 2012 at 10:50 AM, zappfinger 
>> > wrote:
>> >>
>> >> Found it under the tags section, as you mentioned in your previous
>> >> post.
>> >>
>> >> Richard
>> >>
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >> http://csound.1045644.n5.nabble.com/CSPM-Server-tp5717776p5717779.html
>> >> Sent from the Csound - General mailing list archive at Nabble.com.
>> >>
>> >>
>> >> Send bugs reports to the Sourceforge bug tracker
>> >>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >> Discussions of bugs and features can be posted here
>> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >> "unsubscribe
>> >> csound"
>> >>
>> >
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>