webkit*: move webkit-gtk to webkit-gtk41 and shared Makefile.common
The version is the API of the installed webkit-gtk, so webkit-gtk41
for 4.1 (GTK3, libsoup3) and webkit-gtk60 (GTK4, libsoup3).
gtk3 and libsoup2 is not supported any longer (API 4.0) since 2.51.x.
Revert "[clang] Don't add documentation comments to the AST if not requested" (#219807)
Reverts llvm/llvm-project#206363 due to huge compile-time regression.
yelp: update to 42.3.
A newer version is out - this is the last version supporting GTK3,
so use it as a step-point commit.
42.3
====
* Fix CVE-2025-3155 (parrot409, Shaun McCance)
* Switch to meson for builds (Krzesimir Nowak, Michael Catanzaro)
42.2
====
* Updated translations:
ab (Nart Tlisha)
ka (Zurab Kargareteli)
42.1
====
* Fixed URI parsing issue that can lead to crash [#187]
[124 lines not shown]
iocaine: Import iocaine-3.5.1 as www/iocaine
A powerful, programmable defense system that tries to stay out of the way, to
protect backend services and poison crawlers, without interfering with normal
use of the services.
Packaged by Gergely Nagy via <https://git.madhouse-project.org/iocaine/pkgsrc/>,
thanks!
www/webkit-gtk60: import webkit-gtk60-2.52.6
WebKit is an open source web browser engine. WebKit is also the name of
the Mac OS X system framework version of the engine that's used by
Safari, Dashboard, Mail, and many other OS X applications. WebKit's HTML
and JavaScript code began as a branch of the KHTML and KJS libraries
from KDE.
This is the GTK4 port of the engine, API version 6.0.
www/webkit-gtk41: import webkit-gtk41-2.52.6
WebKit is an open source web browser engine. WebKit is also the name of
the Mac OS X system framework version of the engine that's used by
Safari, Dashboard, Mail, and many other OS X applications. WebKit's HTML
and JavaScript code began as a branch of the KHTML and KJS libraries
from KDE.
This is the GTK3 port of the engine, API version 4.1.
In execve(2), attempt to create a realpath buffer for the executable
and place the resulting string on the stack as an auxval. The two
main reasons why the attempt can fail are if the program is started
inside an unlinked directory or if the buffer exceeds PATH_MAX. libc
will be able to find this auxval and provide it in an uncoming
getexecpath(3) API.
ok kettenis beck kirill