why meson of CURRENT needs so many dependencies?

Build dependencies here:
Code: 
/usr/ports/ports-mgmt/pkg
/usr/ports/devel/py-setuptools
/usr/ports/devel/py-wheel
/usr/ports/lang/python312
/usr/ports/devel/py-build
/usr/ports/devel/py-installer

Shown by make build-depends-list.
The result of make all-depends is +900 ports but I never had all of that installed. I think it's the recursive build-deps of all build-deps. Not really useful...
 
MG said:
Build dependencies here:
Code: 
/usr/ports/ports-mgmt/pkg
/usr/ports/devel/py-setuptools
/usr/ports/devel/py-wheel
/usr/ports/lang/python312
/usr/ports/devel/py-build
/usr/ports/devel/py-installer

Shown by make build-depends-list.
The result of make all-depends is +900 ports but I never had all of that installed. I think it's the recursive build-deps of all build-deps. Not really useful...
Click to expand...
Probably do sort -u to exclude duplicates.
 
MG said:
I think it's the recursive build-deps of all build-deps.
Click to expand...
Yeah, it cascades really quickly.

pkg install -A autoconf automake gmake pkgconf gettext-runtime
This usually covers most of build dependencies. It should, at the very least, significantly cull that all-depends list.
 
You must log in or register to reply here.
Back
Top