homebrew/Library/Homebrew/requirements, branch master :beer: The missing package manager for OS X. Add RubyRequirement. 2015-04-21T08:33:41+00:00 Mike McQuaid 2015-04-11T18:18:40+00:00 2f026d3f485a72ec5e3900095684cfcaeb8d3f2b 






FortranDependency: make sure gfortran ends up in PATH
2015-04-08T16:01:23+00:00

Tim D. Smith

2015-04-07T23:37:22+00:00

3d44bdad91b52fcb6b28ff1cb36bbaf33fc44deb

Per requirements.rb:

    >  XXX If the satisfy block returns a Pathname, then make sure that it
    >  remains available on the PATH. This makes requirements like
    >    satisfy { which("executable") }
    >  work, even under superenv where "executable" wouldn't normally be on the
    >  PATH.
    >  This is undocumented magic and it should be removed, but we need to add
    >  a way to declare path-based requirements that work with superenv first.

Fixes homebrew/homebrew-python#170.

Closes #38448.





Per requirements.rb:

    >  XXX If the satisfy block returns a Pathname, then make sure that it
    >  remains available on the PATH. This makes requirements like
    >    satisfy { which("executable") }
    >  work, even under superenv where "executable" wouldn't normally be on the
    >  PATH.
    >  This is undocumented magic and it should be removed, but we need to add
    >  a way to declare path-based requirements that work with superenv first.

Fixes homebrew/homebrew-python#170.

Closes #38448.







Remove unnecessary nil check
2015-03-06T01:48:47+00:00

Jack Nagel

2015-03-06T01:48:47+00:00

493edcf1f7f9a5e6810233ffcbd50c1c0d1823f3

The backticks will either return a string or raise an exception, so
`executable` cannot be nil.





The backticks will either return a string or raise an exception, so
`executable` cannot be nil.







Use env DSL
2015-03-06T01:39:57+00:00

Jack Nagel

2015-03-06T01:39:53+00:00

a60f0d58ce77a6b87424f084e6d0f8d7a9b1560c












java: move java_dependency into a separate file and add Language::Java.java_home_env
2015-02-27T17:42:09+00:00

Xu Cheng

2015-02-26T14:36:04+00:00

8a24a886b6a2a66810a4b09f5f5c78db11ca4058

Also update activemq to test against it

Closes #37218.

Signed-off-by: Xu Cheng <xucheng@me.com>





Also update activemq to test against it

Closes #37218.

Signed-off-by: Xu Cheng <xucheng@me.com>







add inspect to Requirement subclass
2015-02-23T17:39:53+00:00

Xu Cheng

2015-02-23T15:41:43+00:00

97a7565c0d5f4db829503b7ea7ae793e685e0eb2

Closes #37116.

Signed-off-by: Xu Cheng <xucheng@me.com>





Closes #37116.

Signed-off-by: Xu Cheng <xucheng@me.com>







AprRequirement should not generate a build-time dependency
2015-02-02T05:39:04+00:00

Jack Nagel

2015-02-02T05:39:04+00:00

d692f8b94382f0896d295798f9480a26e1c17da0

We want the apr requirement to act as a build-time requirement in case
it is satisfied (that is, the CLT is installed), as the resulting
binaries will link to the system libapr which is always present.

When it is *not* satisfied by the CLT, and we need to install the
formula, we have to treat it as a runtime dependency since the resulting
binaries will link to it.

Fixes #36301.
Fixes #36438.
Closes #36443.





We want the apr requirement to act as a build-time requirement in case
it is satisfied (that is, the CLT is installed), as the resulting
binaries will link to the system libapr which is always present.

When it is *not* satisfied by the CLT, and we need to install the
formula, we have to treat it as a runtime dependency since the resulting
binaries will link to it.

Fixes #36301.
Fixes #36438.
Closes #36443.







AprRequirement should not short-circuit if apr is installed
2015-02-02T05:39:04+00:00

Jack Nagel

2015-02-02T05:39:04+00:00

8444b4f959f1822f10dd7610657091f4c52dbbcc

If apr is installed, we still want to grab it during dependency
resolution in case we need to pass options to the generated dependency.

In other words, it doesn't make sense for the satisfiable condition to
include the default formula, as the default formula is the fallback for
when the requirement is *not* satisfied.





If apr is installed, we still want to grab it during dependency
resolution in case we need to pass options to the generated dependency.

In other words, it doesn't make sense for the satisfiable condition to
include the default formula, as the default formula is the fallback for
when the requirement is *not* satisfied.







Remove message that is never displayed
2015-02-02T05:39:04+00:00

Jack Nagel

2015-02-02T05:39:04+00:00

3c7237e1296074859693189ad605984c6dae9d13

Requirements with default formulae cannot fail the build.





Requirements with default formulae cannot fail the build.







AprRequirement's default formula should be apr-util
2015-02-02T05:39:04+00:00

Jack Nagel

2015-02-02T05:39:04+00:00

f33901731edfa1eb0f89643bd2e17ea981655aeb

This matches the recommendation in the message.





This matches the recommendation in the message.