[MacPorts] #45185: lv2 @1.10.0, lilv @0.20.0, serd @0.20.0, sord @0.12.2, sratom @0.4.6: new ports

MacPorts noreply at macports.org
Sun Sep 28 11:01:41 PDT 2014


#45185: lv2 @1.10.0, lilv @0.20.0, serd @0.20.0, sord @0.12.2, sratom @0.4.6: new
ports
------------------------------------------------+--------------------------
  Reporter:  aggraef@…                          |      Owner:  macports-
      Type:  submission                         |  tickets@…
  Priority:  Normal                             |     Status:  new
 Component:  ports                              |  Milestone:
Resolution:                                     |    Version:  2.3.1
      Port:  lv2core lv2 lilv serd sord sratom  |   Keywords:  haspatch
------------------------------------------------+--------------------------

Comment (by aggraef@…):

 Replying to [comment:3 devans@…]:
 > If, in fact, slv2 will build with lv2 and doesn't conflict with lilv
 then changing its dependency should be sufficient.

 slv2 indeed builds fine against lv2 in lieu of lv2core, by just changing
 the dependency. Suggested changes to the slv2 Portfile attached. I can't
 really test it, though, as there seem to be no ports depending on slv2 in
 MacPorts right now; at least that's what `port echo depends:slv2` says.

 > lv2core should be marked obsolete, replaced by lv2 using the
 [https://guide.macports.org/#development.obsolete-portgroup obsolete
 PortGroup.]

 Ryan, could you (or someone else with commit rights) please take care of
 this, and of updating the slv2 port? Thanks.

 > Concerning maintainership, unless you have made an agreement with
 ryandesign to maintain the ports, I suggest that you add yourself as
 maintainer using the openmaintainer keyword since you do not have (as
 yet?) commit rights.

 Ryan, what would you suggest? I'm fine with it either way.

 > I would be happy to give up maintainership of lv2core and slv2 in your
 favor since you have gone to the work and are much more up to speed on the
 current situation.

 devans, I think that it makes more sense if you keep maintainership of the
 old packages if you're still using them, since I don't and I'm not really
 familiar with slv2 (although I do know the LV2 standard and Lilv pretty
 well).

 Otherwise, if you don't want to keep maintainership, we should ask
 ourselves whether it makes sense to declare lv2core and slv2 as
 unmaintained and up for grabs (if that's possible in MacPorts), as they
 don't seem to be used anywhere. LV2 1.x and Lilv is where all the action
 is now, and has been for quite some time (at least since LV2 1.0 which
 came out in April 2012 IIRC). I'm not aware of any major LV2 host that
 still uses slv2 (in fact its list of dependents in Ubuntu 14.04 is empty
 as well, I just checked that). Of course, there might be some projects out
 there that still use slv2, you never know. But IMHO we can't keep on
 maintaining the old stuff forever, unless there's someone who has a real
 interest in them.

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


More information about the macports-tickets mailing list