https://bugs.kde.org/show_bug.cgi?id=376477

--- Comment #4 from Maurizio Paolini <paol...@dmf.unicatt.it> ---
(In reply to Christoph Feck from comment #3)
> Well, you are not using a separate build directory. If you are not allowed
> to create root files in /home, use a /tmp directory as the build directory.

Thank you.  I am still not used to the concept of a "build" directory.
I think the "old style" sequence

./configure
make
make install

separated build stage (all user-owned files) from eht "install stage"
(everything new is owned by root).

One question: even if I have permissions to create root-owned files in my home,
still it seems to me that mixing user-owned with root-owned files in the same
place (be it /tmp/ or the user /home/user) is not wise.  But I guess this is
a cmake issue.

Another approach would be that the install_manifest.txt be created
with "user" as the owner...

> cd /home/user
> git clone kig
> mkdir /tmp/kig-build
> cd /tmp/kig-build
> cmake -DCMAKE_INSTALL_PREFIX=/usr /home/user/kig
> make
> sudo make install
> cd /home/user
> rm -rf /tmp/kig-build

I tried to report this issue to the cmake developers.  Bug reporting moved to:

https://gitlab.kitware.com/cmake/cmake/issues

> I doubt cmake can be changed to create the "install_manifest.txt" during the
> building, instead of during the installation, but you could report this
> issue to cmake developers via https://cmake.org/Bug

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to