You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now running ldconfig is coupled with installing gnupg component with --sudo option on. This is suboptimal.
One may want to install with --sudo on, but for some reason would rather like skip ldconfig (e.g. on system in which it works in a slightly different way than this scripts expects)
One may want to run scripts as root and without sudo (which may come handy in Docker, esp. when testing)
One may want to build gpgme right after gnupg, in this case ldconfig happens too early
One may want to build some components, but not gnupg (e.g. when building gpgme)
Maybe something else
Anyway, I suppose that running ldconfig should happen after building each individual component, and should be steered by some other option than --sudo. Also, in far future sudo -c could be added for sudoless systems.
The text was updated successfully, but these errors were encountered:
Right now running
ldconfig
is coupled with installinggnupg
component with--sudo
option on. This is suboptimal.--sudo
on, but for some reason would rather like skipldconfig
(e.g. on system in which it works in a slightly different way than this scripts expects)root
and withoutsudo
(which may come handy in Docker, esp. when testing)ldconfig
happens too earlyAnyway, I suppose that running
ldconfig
should happen after building each individual component, and should be steered by some other option than--sudo
. Also, in far futuresudo -c
could be added for sudoless systems.The text was updated successfully, but these errors were encountered: