Re: cmake circular dependency

[Greg Troxel <gdt%lexort.com@localhost>]

Jonathan Perkin <jperkin%pkgsrc.org@localhost> writes:

> I'm pretty sure this is caused by adam's groff update on Sunday, which
> included this addition:
>
>   +.include "../../textproc/uchardet/buildlink3.mk"
>
> uchardet needs cmake to build, so cmake -> curl -> .. groff -> .. cmake.
>
> I don't know what the correct fix is here, other than to again
> reiterate that I firmly believe we should split cmake into two
> packages:
>
>  * devel/cmake-build for building packages, used by mk/
>  * devel/cmake for end users

This sounds good.  Fixing cmake seems impossible; they (and ccache4)
don't seem to understand that build tools need to have small dependency
footprints.

bikeshed: I would call it devel/cmake-minimal, and intend that it be
usable by people to build things, if they don't need the latest and the
crazy features.  But it doesn't actually matter of course.

> with the former being a highly limited build (disabling curl support
> would be another insurance policy against exploitable builds, etc),
> and the latter being the normal batteries-included build for users to
> run outside of pkgsrc.  devel/cmake-build could also be an older LTS
> or similar to avoid unnecessary rebuilds and improve platform support.