On 14/12/16 14:57, Mike Gilbert wrote: > On Wed, Dec 14, 2016 at 9:07 AM, M. J. Everitt <[email protected]> wrote: >> On 14/12/16 13:53, Mike Gilbert wrote: >>> On Wed, Dec 14, 2016 at 7:56 AM, Mart Raudsepp <[email protected]> wrote: >>>> Ühel kenal päeval, K, 14.12.2016 kell 15:35, kirjutas Andrew Savchenko: >>>>> This is not a workaround, but officially recommended practice, from >>>>> man gpg-agent: >>>>> >>>>> You should always add the following lines to your .bashrc or >>>>> whatever initialization file is used for all shell invocations: >>>>> >>>>> GPG_TTY=$(tty) >>>>> export GPG_TTY >>>> Then the packages or eselect pinentry or whatever should be taking care >>>> of it, not have users have to mess with .bashrc to have stuff work. >>> This is not practical. >>> >>> Adding it to the global /etc/bashrc is a bad idea. It would slow down >>> every shell startup (fork/exec), even for users who do not actively >>> use gpg (like root). >>> >>> Also, there is no way to know what shell each gpg user will be using. >>> >> Sounds to me like a perfect candidate for an elog/einfo, no?? > Who reads those? ;-) > > It's not a bad idea though. > I do, but only usually if its the last package of an emerge because otherwise its lost many many thousands of lines upwards. Thank goodness for portage's savelog feature. - Actually that reminds me .. someone mentioned a useful tweak to that, with an appropriate FEATURES switch, it would categorise the output of the logging system .. must look that one up again, or poke the wiki team .......
signature.asc
Description: OpenPGP digital signature
