On Sat, Jan 27, 2018 at 9:22 AM, Albert Graef <aggr...@gmail.com> wrote:
> Sure it’s possible, it just needs some setting up. We even have a version
> of faust in MacPorts, but it’s outdated at this point (mea culpa, I hope
> that I get around updating it over the weekend).
>
As promised, I finally did the migration to the all new and shiny Faust on
MacPorts. The faust-devel update to the latest from master-dev as of today
has already been processed, and the update of the faust port to 2.5.10a is
in the queue and should be available within the next few hours.
Stéphane, I know that my repeated pleas are getting annoying, but even with
my hotfixes the 2.5.10 release is *really* getting a bit long in the tooth
now. There have been 151 commits to master-dev since then, and that's not
just under-the-hood stuff, but some API and architecture changes as well.
So getting a new release out asap which includes these is important IMHO.
Finally, is there an important reason why release tags use the rather
idiosyncratic v2-5-10 scheme? Or was that just an accident? It would be
much easier for us package maintainers if you just use a version number
like 2.5.10 for the tag instead (currently we have to jump through some
hoops to derive the release tag from the package version number using sed
and whatnot). No need to change the existing tags, but it would be nice if
you could keep that in mind when tagging the upcoming release.
Cheers,
Albert
--
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email: aggr...@gmail.com
WWW: https://plus.google.com/+AlbertGraef
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Faudiostream-devel mailing list
Faudiostream-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
