Bug#722430: supercollider: Should use system yaml-cpp

[Felipe Sateler]

On Fri, Sep 13, 2013 at 12:05 PM, Dan S <danstowell+debmm at gmail.com> wrote:
> 2013/9/13 Felipe Sateler <fsateler at debian.org>:
>> On Fri, Sep 13, 2013 at 4:26 AM, Dan S <danstowell+debmm at gmail.com> wrote:
>>> Ah, that's useful. Actually, though, I don't believe porting is
>>> required. The yaml-cpp website says that the old 0.3 API "will
>>> continue to be supported, and will still receive bugfixes", and debian
>>> has libyaml-cpp0.3 available everywhere.
>>
>> In debian, the 0.3 package is built from the same sources, so it is
>> bound to go away at some point. The headers also do not match the 0.3
>> version. I tried building using system yaml-cpp but it failed.
>
> Using system yaml-cpp 0.3, as implemented in my commit?

No, I haven't tried your commit (yet). I tried just enabling system yaml-cpp.

> Curious -
> worked for me. I don't see why 0.3 is bound to go away in the
> medium-term, given that their upstream is so loud about keeping it.

>From debian, at least. The yaml0.3 package is built from the same
source as the 0.5 one, just an older version. That means that 0.3 is
bound to dissappear from debian (unless someone packages it again).

> But I don't mind either way - if you think, then we should reverse my
> commit.

I will upload a version without that commit (hopefully this will avoid
the FTBFS). We can revisit yaml-cpp later.

-- 

Saludos,
Felipe Sateler