[MacPorts] #45364: faustlive-devel: new port

[MacPorts]

#45364: faustlive-devel: new port
------------------------------+--------------------------
  Reporter:  aggraef@…        |      Owner:  ryandesign@…
      Type:  submission       |     Status:  assigned
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:
Resolution:                   |   Keywords:  haspatch
      Port:  faustlive-devel  |
------------------------------+--------------------------

Comment (by aggraef@…):

 Replying to [comment:22 ryandesign@…]:
 > I had assumed that faust2-devel, being the latest version, was a
 superset of all faust functionality, above and beyond faust and faust-
 devel, and that if you have faust2-devel installed there would be no
 reason to go back to faust and faust-devel.

 Faust is an ongoing research project. faust1 is considered stable, while
 faust2 is experimental, the next generation of Faust where new ideas from
 research are incorporated. So faust1 offers a much more limited but stable
 feature set sufficient for supporting most Faust applications, while
 faust2 can occasionally be broken in some (relatively minor) ways but is
 the only way to support more sophisticated applications like FaustLive
 right now.

 This means that most users will use faust1 for regular development, but
 we'd still like to use FaustLive (which depends on faust2) for teaching,
 and faust2 itself for more advanced applications like running Faust dsps
 at near-native speed in JavaScript in a browser, so both must be
 available.

 > Or is faust 2 incompatible with faust 1 in some way?

 The Faust language supported by both implementations is the same, but
 under the hood there are many differences which may result in different
 native code to be generated.

 > What will happen when faust 2 becomes the new stable version?

 Then most likely faust1 will go the way of the dodo, and faust2 will be
 the new faust, and we'll just have to maintain a single port (or two of
 them, to also track the latest development version). But I don't expect
 that to happen anytime soon.

 > Because if the goal is to continue to keep both faust 1 and 2, then they
 should install their files to different locations and not conflict with
 one another like they currently do. And then there will be no problem for
 your scenario.

 Yes, but I don't see that happening anytime soon either, as far as
 upstream is concerned. We could probably use some special installation
 prefixes in the ports, but that's not nice from the usability standpoint
 either. We need a practical solution. What would you suggest? What about
 putting faustlive-devel in the binary package repositories? Wouldn't that
 solve most problems?

-- 
Ticket URL: <https://trac.macports.org/ticket/45364#comment:23>
MacPorts <http://www.macports.org/>
Ports system for OS X