[MacPorts] #47736: [new] EFL 1.14 port
#47736: [new] EFL 1.14 port ----------------------------+-------------------------------- Reporter: pierre.lamot@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: efl | Port: efl ----------------------------+-------------------------------- a port for the last version of the EFL toolkit which improve OSX compatibility -- Ticket URL: <https://trac.macports.org/ticket/47736> MacPorts <https://www.macports.org/> Ports system for OS X
#47736: [new] EFL 1.14 port -----------------------------+-------------------------------- Reporter: pierre.lamot@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: efl | -----------------------------+-------------------------------- Changes (by mf2k@…): * keywords: efl => * version: 2.3.3 => -- Ticket URL: <https://trac.macports.org/ticket/47736#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#47736: [new] EFL 1.14 port -----------------------------+-------------------------------- Reporter: pierre.lamot@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: efl | -----------------------------+-------------------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) Comment: Thanks. I had tried to create a port for efl in 2013 but didn't finish it. Does efl replace any of the older enlightenment libraries I had been updating (e_dbus, ecore, edje, eet, efreet, eina, embryo, evas), until updates stopped appearing last year? You've placed this and the two other port you submitted in #47737 and #47738 in the category "efl", which is not a category we have. Is there another category where this could go? "devel" is a popular catch-all category that could perhaps be used. -- Ticket URL: <https://trac.macports.org/ticket/47736#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#47736: [new] EFL 1.14 port -----------------------------+-------------------------------- Reporter: pierre.lamot@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: efl | -----------------------------+-------------------------------- Comment (by pierre.lamot@…): Hi, Yes the efl package contains theses libraries. I haven't split theses. perhaps I can set them as variants. I put efl in the category because other toolkits were in their own category (gtk, efl, tk, ...) but "devel" is fine for me. -- Ticket URL: <https://trac.macports.org/ticket/47736#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#47736: [new] EFL 1.14 port -----------------------------+-------------------------------- Reporter: pierre.lamot@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: efl | -----------------------------+-------------------------------- Comment (by ryandesign@…): Since the libraries are now distributed together as efl, we should not split them, nor should we have variants related to them. I just wanted to confirm that this was indeed still the same software. Once we add this port, we should mark the old separate ports as `replaced_by efl`. The configure argument `--enable-i-really-know-what-i-am-doing-and-that- this-will-probably-break-things-and-i-will-fix-them-myself-and-send- patches-aba` really needs some explanation... -- Ticket URL: <https://trac.macports.org/ticket/47736#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#47736: [new] EFL 1.14 port -----------------------------+-------------------------------- Reporter: pierre.lamot@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: efl | -----------------------------+-------------------------------- Comment (by pierre.lamot@…): the "enable-i-really-know-..." flags is here to acknowledge that we are using "experimental" feature, In our case, we disabled pulseaudio backend because it hasn't been thoroughly tested on OSX and is probably buggy. A backend has been recently written for coreaudio, but it isn't part of this release. -- Ticket URL: <https://trac.macports.org/ticket/47736#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts