• Describe the issue
  the cmake package on Fedora and EPEL8 provides cmake3, so having a BR on either cmake or cmake3 works fine.

Somehow epel8-playground has a separate, newer cmake3 package though, meaning a package that BRs cmake3 gets this instead of the standard cmake package. And it does not define some macros like %__cmake

e.g. for et
failing epel8-playground build:
root.log - https://kojipkgs.fedoraproject.org//work/tasks/5034/48555034/root.log

DEBUG util.py:623:   cmake3                   x86_64    3.17.2-1.epel8.playground    build     10 M

build.log - https://kojipkgs.fedoraproject.org//work/tasks/5034/48555034/build.log

+ %__cmake -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DBUILD_SHARED_LIBS:BOOL=ON . -DFULL_PROTOBUF:BOOL=ON
/var/tmp/rpm-tmp.mEeOxP: line 42: fg: no job control

succeeding epel8 build:
root.log - https://kojipkgs.fedoraproject.org//work/tasks/5038/48555038/root.log

DEBUG util.py:623:   cmake                     x86_64     3.11.4-7.el8              build     8.1 M

```

• When do you need this? (YYYY/MM/DD)

2020/08/05

• When is this no longer needed or useful? (YYYY/MM/DD)

N/A

• If we cannot complete your request, what is the impact?

epel8-playground potentially inconsistent with epel8 for all packages that pulls in cmake