Comment # 6 on bug 1174581 from Simon Lees

(In reply to Dirk Mueller from comment #3)
> see https://gitlab.kitware.com/cmake/cmake/-/issues/20250
> 
> it is supposed to be relative, us setting it to an absolute path breaks
> documented assumptions. 
> 
> do we still know where/what how things were broken by it? it shouldn't be
> too difficult to fix stuff to use CMAKE_INSTALL_FULL_LIBDIR when it is being
> used outside install commands (where relative work fine).

They are probably not too difficult to fix on a case by case basis but it is a
significant number of packages that break, from also looking at other distro's
its possible that more upstream's are expecting it to be a full path over being
a relative path to the point where years ago fedora decided not to set the
value to anything and force all packages to set it manually so if you can grab
all there spec files you might get some idea.

If someone actually wants to fix it they will probably need to put it into a
staging and slowly go through and fix it for a bunch of upstreams i'm happy for
someone to do this as long as its  not to close to whenever we decide to branch
SLE-16, but currently i'm working on several other projects and don't have
time.