| Newsgroups |
gmane.comp.audio.supercollider.devel |
| Message-ID |
<CAB_zQYu+PWuAQg8Rk9poPAAEo4-oDSBgBXki9EwSsp=AKw54xg@mail.gmail.com> |
Hey Gerard,
I think this makes sense. Let's create a SuperColliderAU repo under the
SuperCollider org and merge 3540+3529 ASAP. If you want I can help you to
set up Travis with a daily or weekly cron job so that any breaking changes
on sc/develop can be caught ASAP.
Regards,
Brian
On Mon, Feb 26, 2018 at 9:33 AM, <[email protected]> wrote:
> Hi. So I have tried using supercollider as submodule in SuperColliderAU
> and it seems to make sense, so it can go to another repo.
>
> I've submitted a new PR to remove the code under
> platform/mac/SuperColliderAU.
> https://github.com/supercollider/supercollider/pull/3540
>
> As explained in the comment, the project still requires the small change
> related with gAsioThread which was submitted separately:
> https://github.com/supercollider/supercollider/pull/3529
>
> So if this seems like a good idea we can discard this one
> https://github.com/supercollider/supercollider/pull/3350
>
>
>
> best,
>
> gerard
>
> 2018-01-07 17:35 GMT+00:00 <[email protected]>:
>
>> "Simplify, simplify, simplify!"
>>
>> My vote would be that if it's possible, it should be a separate repo and
>> submodule.
>>
>> Tom
>>
>>
>>
>>
>> > El 7 ene 2018, a las 08:54, [email protected] escribió:
>> >
>> > Hi all. While discussing the SuperColliderAU PR in the dev meeting, the
>> question about the ideal location of this code was raised. The plugin wraps
>> the supercollider server and thus it is quite sensitive to changes in the
>> server code, this is the reason it was originally added to the project.
>> >
>> > Nowadays, with the help of travis and git submodules it would be less
>> of an issue to maintain it as a separate project, potentially hosted in the
>> SuperCollider github organization. On the other hand, beyond the code in
>> platform/mac, there are a few ifdefs and the SC_AU backend in
>> server/scsynth which are more ingrained.
>> >
>> > Moving the code to a new project would involve re-working the build
>> script, so maybe merging this PR (at least for the moment) would not be too
>> bad anyway, as it fixes code that is not working.
>> >
>> > Any thoughts on this?
>> >
>> >
>> > best,
>> >
>> > gerard
>>
>> _______________________________________________
>> sc-dev mailing list
>>
>> info (subscription, etc.): http://www.birmingham.ac.uk/fa
>> cilities/ea-studios/research/supercollider/mailinglist.aspx
>> archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
>> search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
>>
>
>