Choosable install location (web)

larstobi's Avatar


13 Apr, 2012 08:54 AM

I have installed GPGTools on Mac using your installer, and it has installed itself under /usr/local/MacGPG2. I would like to install it to a different location. Is that possible?

  1. Support Staff 1 Posted by Luke Le on 13 Apr, 2012 10:30 AM

    Luke Le's Avatar


    unfortunately it's not possible to do so at the moment.
    But we're interested in your reasons why you'd want to change the location and it might be changed in future releases if more users express the demand for a custom location.

  2. 2 Posted by Lars Tobias Skj... on 13 Apr, 2012 10:52 AM

    Lars Tobias Skjong-Børsting's Avatar

    One of the reasons I'm asking is that I use Homebrew[1] as a package manager for UNIX tools that Apple didn't include (or don't update) in OSX. This package manager likes to claim /usr/local for itself, and since it will build packages from source, it can get confused by there being unexpected software in /usr/local, and especially the gpg-symlinks in /usr/local/bin.

    It is possible to install Homebrew in a different location, but some software packages won't build as easily, or at all, when dependency libraries are in non-standard locations.


  3. Support Staff 3 Posted by Luke Le on 13 Apr, 2012 10:58 AM

    Luke Le's Avatar

    Hi Lars,

    we're using homebrew ourselves for our MacGPG2 build process and if I'm not mistaken, homebrew should actually not get confused by custom installs as stated on under
    "Can I install my own stuff to /usr/local?"

    However as the FAQ later says, you might run into problems if you install common libraries. This should not be the case with MacGPG2 since only bins are symlinked into the /usr/local/bin folder.

    Hope this helps

  4. 4 Posted by Lars Tobias Skj... on 13 Apr, 2012 11:20 AM

    Lars Tobias Skjong-Børsting's Avatar

    I don't think /usr/local/MacGPG2 will present any problems to any Homebrew builds either, and I manually removed the symlinks it installed into /usr/local/bin (gpg, gpg2, gpg-agent), so that I can build and install gpg with Homebrew. "brew doctor" complains about the /usr/local/MacGPG2 files.

  5. Support Staff 5 Posted by Luke Le on 13 Apr, 2012 11:22 AM

    Luke Le's Avatar

    Is there a special reason why you'd want to build your own gpg?
    Also, could you please post the output of brew doctor so I could have a look at it?

  6. 6 Posted by Lars Tobias Skj... on 13 Apr, 2012 11:35 AM

    Lars Tobias Skjong-Børsting's Avatar

    Building gpg with homebrew is mainly for satisfying package dependencies.

    Here is the output of "brew doctor":

    Warning: "config" scripts exist outside your system or Homebrew directories.
    ./configure scripts often look for *-config scripts to determine if software packages are installed, and what additional flags to use when
    compiling and linking.

    Having additional scripts in your path can confuse software installed via
    Homebrew if the config script overrides a system or Homebrew provided
    script of the same name. We found the following "config" scripts:

  7. Support Staff 7 Posted by Luke Le on 13 Apr, 2012 11:55 AM

    Luke Le's Avatar

    It might help to know that the current nightly (and all next versions of) MacGPG2 does no longer include these config scripts since we've stripped it down to make it much smaller.

    Please try to install the nightly installer and check if homebrew still complains.

  8. 8 Posted by Lars Tobias Skj... on 13 Apr, 2012 12:29 PM

    Lars Tobias Skjong-Børsting's Avatar

    That solves the brew doctor complaints. Thanks! :)

  9. Support Staff 9 Posted by Luke Le on 13 Apr, 2012 12:47 PM

    Luke Le's Avatar

    Closing this discussion. Feel free to open a new one any time!

  10. Luke Le closed this discussion on 13 Apr, 2012 12:47 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac