[MacPorts] #19141: Update libmp4v2

MacPorts noreply at macports.org
Tue May 19 10:35:33 PDT 2009


#19141: Update libmp4v2
---------------------------------+------------------------------------------
 Reporter:  anddam@…             |       Owner:  devans@…           
     Type:  enhancement          |      Status:  assigned           
 Priority:  Normal               |   Milestone:                     
Component:  ports                |     Version:  1.7.0              
 Keywords:                       |        Port:  libmp4v2           
---------------------------------+------------------------------------------

Comment(by devans@…):

 Yes, initial testing shows several incompatibilities.  I am against yet
 another version of this port as we
 have enough cases of problems caused by conflicts between multiple
 versions of ports on the system.  As it is
 now we already have two versions (mpeg4ip and libmp4v2) that have been
 massaged so they do not conflict.

 There are a number of important audio/multimedia applications that depend
 on libmp4v2 so I propose not to
 commit this sort of port until it can be tested and shown to not break any
 of those.  faac is an important
 example.

 So I guess I'm voting for "if it's not broke don't fix it" until we can
 guarantee that no existing ports
 will be broken and there is some positive benefit to a change.  The most
 direct evidence of this would
 be for upstream developers to adopt this version as a dependency, so if
 you feel strongly, I advise
 that you lobby them to switch or at least support this new version in
 addition to the old.

 Another approach would be to commit this as libmp4v2-devel with the
 understanding (as with all devel
 ports) that it conflicts with libmp4v2 and may or may not work.
 Maintainers of dependents of libmp4v2 could
 modify their dependencies using a path rather than port if they desire to
 allow either to satisfy their
 dependency but with the current port being the default until any bugs are
 ironed out.  This would allow
 those that want to try it to do so but not interfere with functionality of
 the currently installed dependent
 ports for the general user.

 I'd like to see some input from the maintainers of the dependent ports
 involved (cc'd) as to their
 feelings about this.

-- 
Ticket URL: <http://trac.macports.org/ticket/19141#comment:6>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list