Changes between Initial Version and Version 1 of Ticket #52404, comment 8


Ignore:
Timestamp:
Aug 7, 2018, 4:23:26 AM (6 years ago)
Author:
kencu (Ken)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #52404, comment 8

    initial v1  
    1 Hi John; the referenced commit did not change `gnucash` to link into `webkit2`; `gnucash` still links against `webkit1`. Some older systems were previously forced to use an old version of `webkit1` due to toolchain issues with `c++11`. We sorted that out, and MacPorts' last available version of `webkit1` now builds on all systems (except PPC), so we now use that version for all systems in ports such as `gnucash`.
    2 
    3 We all hope that one day `gnucash` might no longer need `webkit1` and will either use the more-up-to-date `webkit2` or some other javascript implementation. We look forward to hearing from you / finding out about this when this is possible.
     1Hi John; the referenced commit did not change `gnucash` to link into `webkit2`; `gnucash` still links against `webkit`. Some older systems were previously forced to use an old version of `webkit` due to toolchain issues with `c++11`. We sorted that out, and MacPorts' last available version of `webkit` now builds on all systems (except PPC), so we now use that version for all systems in ports such as `gnucash`.
    42
    53MacPorts has evolved a somewhat confusing array of `webkit` builds over time, which we are trying to simplify.
    64
     5We all hope that one day `gnucash` might no longer need `webkit` and will either use the more-up-to-date `webkit2` or some other javascript implementation. We look forward to hearing from you / finding out about this when this is possible.
     6
    77We recently updated our `webkit2` offerings on MacPorts; `webkit2-gtk` offers version 2.20.3, and `webkit2-gtk-devel` offers 2.21.4. Perhaps one of these versions might pass your tests and we could eventually default to using one of them instead.