On Sun, Apr 03, 2016 at 12:29:11PM +0200, Stefan Sperling wrote: > > I have now run out of patience with this and I'm going to stop working > on it. I see three possible ways forward: > > 1) Accept the so.0.0.0 files generated by ardour and hope that upstream > will update waf eventually. The current git master still uses waf 1.6. > I don't think this matches our port guidelines but perhaps we can make > an exception? > > 2) Remove the port. Perhaps re-add it later if this situation has been > resolved upstream. > > 3) Someone else picks up on this and tries to wrangle a working waf into > my work-in-progress port (drop me a mail if you want to do this). > > If this post is met with silence, or with general approval of option 2, > I'm going to pursue option 2. It's sad, because ardour is a great example > of a complex open source tool which meets professional needs. > I like having it available in OpenBSD for this reason. > > But I suppose not many people run their recording studios on OpenBSD anyway, > and there are many other projects worth spending my time on...
ardour depends on jackd which wasn't stable enough last time I tried to use it; this makes ardour not very useful. Fixing jackd is on my todo list, so keeping ardour would be nice for experimenting; even an old version would be better than nothing. Meanwhile upstream might switch to a working waf version, who knows. my 2 cents
