Ben Cotton wrote:
> == Summary ==
> <code>%cmake</code> macro will be adjusted (<code>-B</code> parameter)
> to use separate build folder (already standardized
> <code>%{_vpath_builddir}</code> macro). Additionally,
> <code>%cmake_build</code>, <code>%cmake_install</code> and
> <code>%ctest</code> macro will be created (and backported to the older
> supported Fedora releases) to perform various operations that are
> commonly used with CMake in a backend-agnostic (Makefiles, Ninja,
> etc.) way.
>
> Packages that will stop building are trivial to fix and will be
> adjusted either by maintainers or change owners.
>
> == Owner ==
> * Name: [[User:ignatenkobrain|Igor Raits]], [[User:besser82|Björn
> Esser]], [[User:ngompa|Neal Gompa]]
> * Email: [email protected], [email protected],
> [email protected]
How does this affect the many packages that already build in a separate
build folder manually? There are even several specfile templates that
contain the boilerplate for that.
And why is it worth making a potentially incompatible change to the %cmake
macro when it can already be done with the existing one?
Kevin Kofler
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
