Home → Stable →

GPGTools Installation

• Edit

outer

27 Nov, 2012 06:58 PM

MacBookPro9,1; Mountain Lion OS X 10.8.2 (12C3006)

GPGTools-ML1.pkg 2012-10-05

I note with not inconsiderable displeasure, not to say the least dismay,
that this install has broken your promise to me not to overwrite any
preëxisting pgp2 installations in /usr/local/bin. Instead, all my locally
installed instances in /usr/local/bin have been replaced by symbolic
links into the heart of /usr/local/MacGPG2/. Now I have to go back
and recompile everything, and reinstall it. Will GPGTools still work?

Why? On Earth?

1. Support Staff 1 Posted by Luke Le on 27 Nov, 2012 07:21 PM

   

   Hi Outer,

   is it Not possible to simply recreate the original symlinks?
   Since everything related to MacGPG2 resides within /usr/local/MacGPG none of your self compiled files should have been overwritten (except for the symlinks of course)

   When you install GPGTools you can decide whether to install MacGPG or not.
   We've assumed that's a safe enough option for savvy and non-savvy users alike.

   • Edit

2. 2 Posted by Tony on 27 Nov, 2012 08:26 PM

   

   This comment was split into a new discussion: GPGMail for Outlook 2011

   Just curious, will GPGTools for Mac work with Outlook 2011 for Mac? I've been using it with Outlook 2010 for Windows, and I'm hoping to continue the same fine experience.

   Tony

   • Edit

3. 3 Posted by outer on 27 Nov, 2012 11:09 PM

   

   OK, ongoing discussion, great!

   Just tried recompiling gpg2... oops, i need libgcrypt 1st
   Just tried recompiling libgcrypt... oops, need libgpg-error 1st
   Just tried recompiling gpg2 again... oops need lib assuan 1st

   and so on and so on. this is simply unacceptable, even for a
   beta-test program.

   • Edit

4. Support Staff 4 Posted by Luke Le on 27 Nov, 2012 11:19 PM

   

   Hi Outer,

   I don't think I can follow you.
   Are you trying to compile MacGPG from our github sources?
   Or are you trying to compile it manually?

   What is unacceptable for a beta program and how is manually compiling related to our GPGMail preview version?

   We'll be glad to help you get things sorted out, but need some more detailed information on what's not working and what you're trying to do

   • Edit

5. 5 Posted by outer on 28 Nov, 2012 12:34 AM

   

   No, not at all. I am objecting to the GPGTools installer replacing my self-compiled binaries in /usr/local/bin/ with symbolic links to binaries in /usr/local/MacPGP2. The original files were deleted, gone. I'd thought that the team had promised its Users that this would never happen: GPGTools would never interfere or override a previous User installation of either gpg or gpg2 in /usr/local/bin/. Are you with me so far? Am I wrong?

   • Edit

6. Support Staff 6 Posted by Luke Le on 28 Nov, 2012 12:39 AM

   

   I can partly understand your frustation but am wondering why you didn't decide to not install MacGPG2 when using the GPGTools Installer which is an option.

   When installing MacGPG2 we have to create the appropriate symlinks in order to assure that it will work for all tools using gpg on your machine, which includes but is not limited to our own tools. That's where the decision stems from.
   In the past we've installed into /usr/local which was the big problem we've regretted and later fixed. So now only /usr/local/bin is touched and only for creating symlinks pointing into /usr/local/MacGPG2.

   I don't understand your recompiling errors or messages... could you elaborate on those.

   • Edit

7. 7 Posted by outer on 28 Nov, 2012 01:39 AM

   

   The basic question is whether I can maintain a "reference" implementation of gpg2 alongside (together with) a GPGTools implementation of gpg2.

   The recompiling error messages are irrelevant to this discussion, they simply reflect my frustration at having to recompile and reinstall gpg2.

   • Edit

8. Support Staff 8 Posted by Luke Le on 28 Nov, 2012 01:43 AM

   

   You can, but only if you deselect MacGPG2 when installing new GPGTools packages or recreate the symlinks after. There should be no need to recompile and I still don't really understand why you have to now.

   • Edit

9. Support Staff 9 Posted by Luke Le on 28 Nov, 2012 01:44 AM

   

   Also you might consider using our MacGPG2 repository as starting point.
   Checkout branch homebrew. That way you can easily build MacGPG or any version of gnupg by simply adjusting some configuration files and deactivating the patches specific to MacGPG.

   • Edit

10. Support Staff 10 Posted by Steve on 20 Jan, 2013 07:34 PM

    

    No further user feedback. Closing.

    @Outer: Should your problem persist, feel free to re-open this discussion any time.

    All the best,
    steve

    • Edit

11. Steve closed this discussion on 20 Jan, 2013 07:34 PM.