Opened 9 years ago
Closed 9 years ago
#48206 closed defect (fixed)
qt4-mac, qt5-mac: ports no longer conflict
Reported by: | dbevans (David B. Evans) | Owned by: | michaelld@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | mdeaudelin (Mathieu Deaudelin-Lemay), Polyergic (Shad Sterling), springermac (Jonathan Springer) | |
Port: | qt4-mac qt5-mac |
Description
While doing some testing relative to #47025, I found that qt4-mac and qt5-mac can now, apparently, be active simultanously without any conflict. The ports still claim that they conflict.
Is there any reason why the conflicts statements in these two ports shouldn't be changed to allow simultaneous installation? Doing so allows poppler-qt4-mac and poppler-qt5-mac as proposed in #47025 to build and install in parallel.
Change History (6)
comment:1 Changed 9 years ago by michaelld (Michael Dickens)
comment:2 Changed 9 years ago by dbevans (David B. Evans)
Thanks for the update. This is good news and certainly a better approach. Let me know when it's safe to go ahead. In the meantime, I'll be waiting expectantly.
comment:6 Changed 9 years ago by dbevans (David B. Evans)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Conflict removed in r142934.
Note: See
TracTickets for help on using
tickets.
This is true from a certain perspective: qt4 installs into ${prefix} and qt5 into ${prefix}/libexec/qt5-mac. That said, there will be projects which try to auto-detect the Qt install, looking for ${prefix}/bin/qmake and using it if found -- no matter the user's settings otherwise (e.g., QMAKE=${prefix}/libexec/qt5-mac/bin/qmake). So, we're better off just moving Qt4 to be in ${prefix}/libexec/qt4-mac (or something like it). I'm well on my way down that path, and expect to have it done sometime next week. Thus, while we -could- change both ports so that they don't conflict -right now-, I'd be just as happy to wait until my "big commit" is in place & qt4 is moved to its own space. I expect there will be plenty of issues with the "big commit", no matter how hard I try to make it otherwise. I also expect we'll have issues with removing the conflict ... so, why not just wait until there really is no conflict?