Quote of the week
Quote of the week
Posted Apr 25, 2019 15:26 UTC (Thu) by mathstuf (subscriber, #69389)In reply to: Quote of the week by nix
Parent article: Quote of the week
Is that really Meson's fault or is it more on the GTK Meson input rules that are only attached to the `install` target? Granted, running ninja itself has some issues as root[1]. However, personally, I almost never do a `sudo make install` anyways since I install software like ports into my home directory (and it needs added to PATH and friends manually). The system is managed by the package manager. I manage my home directory.
Posted Apr 26, 2019 11:48 UTC (Fri)
by nix (subscriber, #2304)
[Link]
And things like CPAN.pm and pip and gem make this even harder :/
Quote of the week
Is that really Meson's fault or is it more on the GTK Meson input rules that are only attached to the `install` target?
Oh, almost certainly the latter -- but last I checked this stuff was managed by a plugin that was actually part of the Meson source tree, so it's Meson's doing in any case. :)
However, personally, I almost never do a `sudo make install` anyways since I install software like ports into my home directory (and it needs added to PATH and friends manually). The system is managed by the package manager. I manage my home directory.
Even if you're using a package manager, you should still be doing make install DESTDIR=... as non-root and doing a final, non-customizable-by-the-package-itself install phase of some kind as root (rpm installation, grafting, stowing, whatever, and the usual rebuilding of systemwide caches like fontconfig, mime-install, ldconfig etc as needed). However, this can lead to extra complexity and the need for either per-package customization work or some sort of LD_PRELOAD interposer like fakeroot if make install installs things with unusual ownerships or permissions, as some still do.