#46239: qca and qca-ossl adaptations to qt4-mac +concurrent ----------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: haspatch Port: qca, qca-ossl | ----------------------------+-------------------------------- Comment (by rjvbertin@…): Re: qca.diff: if a Portfile cannot verify properly whether an optional dependency is installed, that might be an argument to turning qt4-mac- transitional back into a variant. Other ports may also want to replace a moved shared library (plugin, etc) with a symlink to the object in its new location... -- Ticket URL: <https://trac.macports.org/ticket/46239#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X

#46239: qca and qca-ossl adaptations to qt4-mac +concurrent ---------------------------+------------------------- Reporter: rjvbertin@… | Owner: michaelld@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: qca qca-ossl | ---------------------------+------------------------- Comment (by mk@…): How about this one, René, can these patches be committed without doing any harm to the current qt4-mac port? -- Ticket URL: <https://trac.macports.org/ticket/46239#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X

#46239: qca and qca-ossl adaptations to qt4-mac +concurrent ---------------------------+------------------------- Reporter: rjvbertin@… | Owner: michaelld@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: qca qca-ossl | ---------------------------+------------------------- Comment (by rjvbertin@…): Replying to [comment:6 rjvbertin@…]:

It should be fine, the changes not protected by a test boil down to setting the default explicitly if you see what I mean. But let me check if I shouldn't update the patches. They're 6 months old by now.

All fine as far as I can see. `port:qca` contains a context-sensitive variant that is made the default when my `qt4-mac-transitional` port is installed. That's not entirely politically correct, but as it's a temporary feature (and that transitional port is not currently a published port) I'm hoping it dosing raise too much ire.[[BR]] Alternatively I presume I could obtain the variant's effect (creation of a single symlink) in a post-activation stage. -- Ticket URL: <https://trac.macports.org/ticket/46239#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X

#46239: qca and qca-ossl adaptations to qt4-mac +concurrent ---------------------------+------------------------- Reporter: rjvbertin@… | Owner: michaelld@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: qca qca-ossl | ---------------------------+------------------------- Comment (by rjvbertin@…): I've uploaded an initial version of an update to QCA 2.1.0 to my github repo. Only thing not tested yet are the universal builds. There appear to be no API changes, but I haven't yet done extensive testing of existing applications against the new library version. Anyone interested in trying this new version? -- Ticket URL: <https://trac.macports.org/ticket/46239#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X

#46239: qca and qca-ossl adaptations to qt4-mac +concurrent ---------------------------+------------------------- Reporter: rjvbertin@… | Owner: michaelld@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: qca qca-ossl | ---------------------------+------------------------- Comment (by rjvbertin@…): Do as you wish ... -- Ticket URL: <https://trac.macports.org/ticket/46239#comment:11> MacPorts <https://www.macports.org/> Ports system for OS X

#46239: qca and qca-ossl adaptations to qt4-mac +concurrent ---------------------------+------------------------- Reporter: rjvbertin@… | Owner: michaelld@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: qca qca-ossl | ---------------------------+------------------------- Comment (by michaelld@…): Please give me a few days to catch up (from being on vacation the last few weeks) & I'll check these out & do some commits. QCA has been on my queue for a long time to get updated, and if René's patches do the trick then I'm all for them. -- Ticket URL: <https://trac.macports.org/ticket/46239#comment:13> MacPorts <https://www.macports.org/> Ports system for OS X

#46239: qca and qca-ossl adaptations to qt4-mac +concurrent ---------------------------+------------------------- Reporter: rjvbertin@… | Owner: michaelld@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: qca qca-ossl | ---------------------------+------------------------- Comment (by michaelld@…): René: Yes, I'm kinda snowed under both in emails as well as MP updates to review and/or install; it might be a day or 2 before I get to the Qt4 stuff. I appreciate you doing standby duty; I'm sure we'll need folks to address Qt4 build issues once the changes are in place. Does what you wrote mean you are available for the next week or starting in about a week? I'm hoping the latter, which would actually be a good match for my current schedule. -- Ticket URL: <https://trac.macports.org/ticket/46239#comment:15> MacPorts <https://www.macports.org/> Ports system for OS X

#46239: qca and qca-ossl adaptations to qt4-mac +concurrent ---------------------------+------------------------- Reporter: rjvbertin@… | Owner: michaelld@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: qca qca-ossl | ---------------------------+------------------------- Comment (by michaelld@…): I'm hoping that we can rev-bump many of the qt4-mac dependencies to take care of 90%+ of the dependent ports. I'm quite sure there will be difficult ones, which is where having folks on standby to help with the load will be useful. I think I can start working on this Tuesday, with the goal of committing Wednesday or Thursday depending on complexity. This ticket's issue will likely be included in one of the final commits, to get it working with the new Qt4 location. Good luck with your family! -- Ticket URL: <https://trac.macports.org/ticket/46239#comment:17> MacPorts <https://www.macports.org/> Ports system for OS X

#46239: qca and qca-ossl adaptations to qt4-mac +concurrent ---------------------------+------------------------- Reporter: rjvbertin@… | Owner: michaelld@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: qca qca-ossl | ---------------------------+------------------------- Changes (by michaelld@…): * status: new => closed * resolution: => fixed Comment: This ticket's issue has been fixed/surpassed by r145233. -- Ticket URL: <https://trac.macports.org/ticket/46239#comment:19> MacPorts <https://www.macports.org/> Ports system for OS X

#46239: qca and qca-ossl adaptations to qt4-mac +concurrent ---------------------------+------------------------- Reporter: rjvbertin@… | Owner: michaelld@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: qca qca-ossl | ---------------------------+------------------------- Comment (by michaelld@…): Hmm ... well, the only thing installed into the Qt4/Qt5 directory is the mkspec file. Everything else is installed into just ${prefix} subdirectories. The plugins are installed into /opt/local/share/qca/plugins/crypto . None of the plugins have a self-id according to otool. Not sure what else is needed. Can you test to verify that they work? -- Ticket URL: <https://trac.macports.org/ticket/46239#comment:21> MacPorts <https://www.macports.org/> Ports system for OS X

#46239: qca and qca-ossl adaptations to qt4-mac +concurrent ---------------------------+------------------------- Reporter: rjvbertin@… | Owner: michaelld@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: qca qca-ossl | ---------------------------+------------------------- Comment (by rjvbertin@…): On a more general note, re: the comments on Debug builds. Qt's debug+release frameworks builds really seem geared towards people who do development on Qt itself. They're very cumbersome to use for debugging dependent software in my experience (I couldn't get dyld to load all _debug framework "payloads") and is just about as viral as +universal in that it causes all dependents to build that way. This is not related to the issue at hand, but just how many MacPorts users have a need to do full source-level debugging of Qt code? I know only one -- me O:-), and I simply use a release build with debug info. That's good enough; I can step through the code and then decide where I have to add qDebug() calls to inspect C++ variables. I don't think that a full debug build would make it easier to understand what's going on in code that makes such extensive use of class instances which are almost impossible to inspect in a debugger (that's not gdb). -- Ticket URL: <https://trac.macports.org/ticket/46239#comment:23> MacPorts <https://www.macports.org/> Ports system for OS X