#34805: poedit-devel --------------------------------------------+------------------------------- Reporter: mojca.miklavec.lists@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: poedit-devel --------------------------------------------+------------------------------- Comment(by raimue@…): Replying to [comment:4 mojca.miklavec.lists@…]:
That one is easy. See https://github.com/vslavik/poedit/commit/08fcc8bf4c93f1ca0628663b76609166a62.... But I believe there are other problems as well and it might be easier to just take the latest version than to backport all patches from latest version to 1.4.6.
Thanks for the link! However, I ran into further problems as you assumed correctly. So this is not enough yet. I will probably look into this later again, but don't have the time at the moment.
* Renaming to Poedit-devel.app is a good idea, but cannot be combined with wxWdigets-devel as default at the same time as that would defeat the purpose.
I don't understand.
I see two options: a) Renaming the provided application bundle to Poedit-devel.app removes the conflict with poedit.[[BR]] b) Making wxWidgets-devel the default adds a conflict with poedit (which requires wxWidgets). When implementing option b), option a) is not necessary anymore as poedit and poedit-devel would conflict anyway because of the dependency on wxWidgets and wxWidgets-devel, respectively.
How do you do it without checksum to prevent complaints during installation?
The key is using `fetch.type git`. However, the github port group should already take care of that, just remove the checksums line.
wxWidgets 2.9.3 (and consequently any given port depending on them) cannot be compiled with clang.
Does the problem only apply to wxWidgets compilation or is the error in the provided header files? Why is that a problem for dependents?
This has been solved in 2.9.4, but that version hasn't been released yet. I have a version with patches ready in case that it will take another few months for them to release 2.9.4 (but it is not compatible with Tiger any more).
Tiger is a legacy platform and if upstream software drops support for it, we do not have obligations to support it any longer. -- Ticket URL: <https://trac.macports.org/ticket/34805#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS