On Mon, Apr 28, 2014 at 4:27 PM, Gordon Sim <[email protected]> wrote: > On 04/28/2014 09:15 PM, Justin Ross wrote: > >> On Mon, Apr 28, 2014 at 4:07 PM, Gordon Sim <[email protected]> wrote: >> >> On 04/28/2014 08:43 PM, Rafael Schloming wrote: >>> >>> I'm pretty opposed to getting rid of SYSINSTALL_BINDINGS though not only >>>> to >>>> avoid spurious bug reports, but also because it is the only foolproof >>>> way >>>> we have to get someone up and running quickly that isn't highly >>>> dependent >>>> on their system configuration. The install instructions are pretty much >>>> just: >>>> >>>> cmake SYSINSTALL_BINDINGS=ON >>>> make >>>> sudo make install >>>> >>>> >>> Can SYSINSTALL_BINDINGS=ON not be automatically inferred if no >>> CMAKE_INSTALL_PREFIX is specified? Or does CMAKE_INSTALL_PREFIX always >>> have >>> a value, even if not set explicitly? >>> >>> >>> That would overwrite OS-reserved file locations. >> > > That's what make install (without an explicit prefix) always does, isn't > it? > > If I don't specify a prefix, I expect things to be installed into the > system wide default locations for whatever it is. If I specify a prefix, I > expect to to be relative to that and expect to have to set various path > variables to locate 'my' install. > > No, the default prefix is typically /usr/local, and indeed /usr/local is set aside for this use. For instance, setup.py install by default installs with the prefix /usr/local on unix machines.
The reason for this is I think pretty clear: most users of popular distros won't tolerate having their package-system-managed files get clobbered. It will mess up your OS install in a hurry.
