[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@…):

 Yes, I see what you mean. But sound2faust then is the least of our
 concerns. Statically linking against libfaust, libOSCFaust and
 libHTTPDFaust is a much more serious problem in your scenario, since these
 are much more likely to change between faust2 revisions, potentially
 making faustlive-devel's behavior depend on the particular faust2-devel
 version it was built with.

 But keeping faust2-devel out of faustlive-devel's runtime dependencies is
 really important. It's so important for me that I'd rather keep updating
 both ports in lockstep. Hence my question whether MP actually enforces an
 upgrade of a port when one of its build dependencies is updated.

 Replying to [comment:12 ryandesign@…]:
 > And we want deterministic repeatable builds. Imagine this scenario:
 >
 >  * on 20141015 we update faust2-devel to version 20141015
 >  * on 20141016 we update faustlive-devel to version 20141016 which is
 compatible with faust2-devel 20141015
 >  * on 20141017 user X installs faustlive-devel 20141016 and gets a
 working port
 >  * on 20141018 we update faust2-devel to version 20141018 which is not
 compatible with faustlive-devel 20141016 anymore
 >  * on 20141019 user Y installs faustlive-devel 20141016 and gets a non-
 working port; user X's installation still works fine
 >
 > We don't want two different users installing the same version of a
 package to have different results, which is why embedding another port's
 files is usually undesirable and why I would use a symlink instead.

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