brew/Library/Homebrew, branch 0.9.3 🍺 The missing package manager for macOS Homebrew 0.9.3 for superenv 2012-08-29T17:08:46+00:00 Adam Vandenberg 2012-08-29T17:08:46+00:00 1eb808c109466a6f774e2171510b1a3202853509 






`brew sh`: a shell with superenv loaded
2012-08-29T16:41:38+00:00

Max Howell

2012-08-29T15:21:15+00:00

bdd6193587b22e59c82e5b53b00fa7ceb2c90a54

If you need to build software on OS X by hand, a brew shell is the way to do it.

Closes Homebrew/homebrew#14381.





If you need to build software on OS X by hand, a brew shell is the way to do it.

Closes Homebrew/homebrew#14381.







superenv only adds X11 paths if required
2012-08-29T16:41:37+00:00

Max Howell

2012-08-29T15:19:39+00:00

a360a41472cad35dfdf81d1551df55b442a22ba1

Since we are moving towards only depending on X11 for X-headers, superenv now doesn't automatically add X11 compilation. I was reluctant to do this, but it is the right thing to do now that X11 is not automatically installed by OS X or Xcode.

I didn't implement ENV.x11 because the order that the X headers are inserted is important. It must be done at initial setup to ensure that brewed versions of e.g. freetype and Cairo are used and not the ones installed by XQuartz.





Since we are moving towards only depending on X11 for X-headers, superenv now doesn't automatically add X11 compilation. I was reluctant to do this, but it is the right thing to do now that X11 is not automatically installed by OS X or Xcode.

I didn't implement ENV.x11 because the order that the X headers are inserted is important. It must be done at initial setup to ensure that brewed versions of e.g. freetype and Cairo are used and not the ones installed by XQuartz.







Doctor suggest `git clean -f` if unstaged files
2012-08-29T16:41:37+00:00

Max Howell

2012-08-29T13:03:41+00:00

b834027b179c72c47339b7dd65c7cbf2b8ed4b0a

This is safe, I tested various scenarios, including Homebrew installed in ~. The only files that are removed are unexpected files in Homebrew's already managed directories.





This is safe, I tested various scenarios, including Homebrew installed in ~. The only files that are removed are unexpected files in Homebrew's already managed directories.







Warn user if they set CFLAGS, etc. with superenv
2012-08-29T16:41:37+00:00

Max Howell

2012-08-28T23:29:10+00:00

7d8954d74caf59fdc93dae255e3b5fee328c5972

Since we remove some CFLAGS under their noses, this would otherwise be quite confusing.

Notably, this will now trigger in numerous formula. Sucks.





Since we remove some CFLAGS under their noses, this would otherwise be quite confusing.

Notably, this will now trigger in numerous formula. Sucks.







Speed up brew instantiation
2012-08-29T16:41:36+00:00

Max Howell

2012-08-28T12:31:14+00:00

24bcc694e58024f47315474610ff8514fc65d074

Adding MacOS.dev_tools_path to our PATH was slow. We no longer need to do this because of the previous commit making a script wrapper for git and svn. It was slow because the function calls out to lots of slow utilities to determine this path.





Adding MacOS.dev_tools_path to our PATH was slow. We no longer need to do this because of the previous commit making a script wrapper for git and svn. It was slow because the function calls out to lots of slow utilities to determine this path.







Always find git and svn without trying hard
2012-08-29T16:41:36+00:00

Max Howell

2012-08-28T13:50:03+00:00

672388d4f71e810d0f742518b5cd4a5aa7de6e04

Two wrapper scripts that find git and svn using the ENV variables we support and then searching through the PATH and looking inside Xcode.app if necessary.

Now just calling git or svn in Homebrew code will find and exec the right tool and we can stop fussing.

Apologies to @adamv who is probably unimpressed that the cmds directory has non-commands in it now. If it's consolation these are temporary pending some more work on superenv whereby some more directories are created under the superenv root.





Two wrapper scripts that find git and svn using the ENV variables we support and then searching through the PATH and looking inside Xcode.app if necessary.

Now just calling git or svn in Homebrew code will find and exec the right tool and we can stop fussing.

Apologies to @adamv who is probably unimpressed that the cmds directory has non-commands in it now. If it's consolation these are temporary pending some more work on superenv whereby some more directories are created under the superenv root.







Attempt to fix opt link if absent
2012-08-29T16:41:36+00:00

Max Howell

2012-08-27T16:02:57+00:00

0efd1b9efefe107f637784c90643d512bd060c2c

This is mainly to prevent errors when users for the transitionary period where most installed kegs do not have an opt link.





This is mainly to prevent errors when users for the transitionary period where most installed kegs do not have an opt link.







Ensure mktemp cleans up after itself
2012-08-29T16:41:36+00:00

Max Howell

2012-08-23T16:47:36+00:00

d89b3272f441ebdc71d0ffb0448dd1c364f1ca52

Ignore interrupts.





Ignore interrupts.







If installed but not linked, say so
2012-08-29T16:41:35+00:00

Max Howell

2012-08-23T13:02:24+00:00

336c4d1b05df9db2e13ffe88607f5e44493f3b8f

Rationale: if ack is unlinked but installed, typing ack does nothing, but then user tries to install and it says it is already installed. What gives? The user thinks.

Formula ending up unlinked can happen due to failures during the link phase and we recommend unlinking formula for conflicts. So common enough to justify this amendment.





Rationale: if ack is unlinked but installed, typing ack does nothing, but then user tries to install and it says it is already installed. What gives? The user thinks.

Formula ending up unlinked can happen due to failures during the link phase and we recommend unlinking formula for conflicts. So common enough to justify this amendment.