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.
Right now running
ldconfigis coupled with installinggnupgcomponent with--sudooption on. This is suboptimal.--sudoon, 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)rootand withoutsudo(which may come handy in Docker, esp. when testing)ldconfighappens too earlyAnyway, I suppose that running
ldconfigshould happen after building each individual component, and should be steered by some other option than--sudo. Also, in far futuresudo -ccould be added for sudoless systems.