update to vim-9.1.1478, merging the -lang subpackage into the main
package while there. the byte saving in the default install isn't worth
the extra hassle at update time (which is already tricky due to evim,
gvim and friends which are only in the gui installs).
pvk@ sent me a diff to fix some issues with missing dir creations due
to badly placed files, but I thought I'd go with this approach instead.
updates handled with @conflict @pkgpath as needed (relying on the old
packages which had @pkgpath ${BASE_PKGPATH} that means they match nicely
with the default new pkgpaths, avoiding the need for messy flavour
handling).
editors/nano: update to 8.5
Improvements:
- Anchors are saved and restored (when --positionlog is active).
- Key combos ^O^Q and ^X^Q cause an exit status of 2.
now fails on 32-bit archs; set ONLY_FOR_ARCHS
../src/_backend_agg_wrapper.cpp:253:17: error: non-constant-expression cannot be narrowed from type 'unsigned int' to 'long' in initializer list [-Wc++11-narrowing]
update to pebble-2.8.0 (switching from github.com/letsencrypt/pebble
to github.com/letsencrypt/pebble/v2, thanks go ecosystem...) which
doesn't have such ancient deps as the previous 1.0.1 and is able to
build on a wider range of archs.
Unbreak linking with ld.lld and newer pkgconf
pkgconf(1) doesn't outputs private libs (needed for static linking) by
default, as opposed to our base pkg-config(1). So specify missing
libvorbis and libogg which are directly referenced by xmms2-ripper.
MFC update to python-3.12.11 for 'tarfile' fixes (arbitrary filesystem
writes outside the extraction directory during extraction with
filter="data", etc).
revert ninja to 1.11.1, discussed with robert
Various bulk builders hit build failures in chromium and friends, most
likely caused by this change from 1.12.0 in combination with missing
build dependencies in upstream chromium:
-Critical path scheduler which orders the jobs by their runtime history
-This may break your build if you haven't specified your dependencies
