- Timestamp:
- 07/30/2015 03:20:25 AM (9 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- b82dab5
- Parents:
- a6b91ea6
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
x/lib/webkitgtk2.xml
ra6b91ea6 r1ee4839 132 132 <para> 133 133 Upstream standard now is to link this package against <application>GTK+ 134 3</application>. However, for backward compatibility, man uusers need134 3</application>. However, for backward compatibility, many users need 135 135 also another instance, linked to <application>GTK+ 2</application>. Both 136 can be installed in the same system, without problem. However, some136 can be installed in the same system, without any problems. However, some 137 137 packages can alternatively be linked to either one. Here, both build 138 138 methods are presented and recommended to be built, but if you know which
Note:
See TracChangeset
for help on using the changeset viewer.