Changes between Initial Version and Version 1 of Ticket #51619, comment 30
- Timestamp:
- Jan 1, 2017, 1:27:10 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #51619, comment 30
initial v1 6 6 7 7 {{{ 8 if {[ something]} {8 if {[port:qt5_is_installed]} { 9 9 PortGroup qt5 1.0 10 10 return 11 } 12 }}} 13 14 and in `qt5-1.0.tcl` 15 16 {{{ 17 if {[port:qt5_is_installed] || [variant_isset qt5kde]} { 18 if {[port_opts_out]} { 19 return -code error "Incompatible qt5-kde port installed" 20 } else { 21 PortGroup qt5 1.0 22 return 23 } 11 24 } 12 25 }}} … … 17 30 The appeal is that we will each have more leeway in the choice of the exact implementation like for instance `qt5.depends_component` which means it wouldn't have to implement "adaptive depspecs". 18 31 19 The crucial condition here is of course that we must both agree to transfer control to the other PG when that is dictated by the installed Qt5 port or user preference indicated in some other way. I have no problem with that (it's what I'm aiming at already) but I would have preferred to shoulder that responsibility (through a shared PG) and not burden others with it because unhappy changes could cause considerable breakage in KF5 functionality. 32 The crucial condition here is of course that we must both agree to transfer control to the other PG when that is dictated by the installed Qt5 port or user preference indicated in some other way.I have no problem with that (it's what I'm aiming at already) but I would have preferred to shoulder that responsibility (through a shared PG) and not burden others with it because unhappy changes could cause considerable breakage in KF5 functionality. 33 It will probably be necessary too to protect the PGs against loading them multiple times to avoid unexpected situations where for some reason the 2 PGs are loaded in succession. 20 34 21 35 We might do something similar for the qmake5 PG too.