brew/Library/Homebrew/requirements/fortran_requirement.rb

require "requirement"

class FortranRequirement < Requirement
  fatal true

  default_formula "gcc"

  env { ENV.fortran }

  satisfy build_env: false do
    which(ENV["FC"] || "gfortran")
  end
end
Core files style updates. Closes Homebrew/homebrew#42354. Signed-off-by: Mike McQuaid <mike@mikemcquaid.com> 2015-08-03 13:09:07 +01:00			`require "requirement"`
Add :fortran requirement 2013-06-23 18:35:20 -07:00
Rename requirements named Dependency. Dependency is another similar, related class and it's super confusing to have some Requirements that are named Dependency. Closes Homebrew/homebrew#38891. Signed-off-by: Mike McQuaid <mike@mikemcquaid.com> 2015-06-15 09:56:04 +01:00			`class FortranRequirement < Requirement`
Add :fortran requirement 2013-06-23 18:35:20 -07:00			`fatal true`

Core files style updates. Closes Homebrew/homebrew#42354. Signed-off-by: Mike McQuaid <mike@mikemcquaid.com> 2015-08-03 13:09:07 +01:00			`default_formula "gcc"`
Add :fortran requirement 2013-06-23 18:35:20 -07:00
			`env { ENV.fortran }`

rubocop --auto-correct all hash-rocket usage. 2016-09-17 15:32:44 +01:00			`satisfy build_env: false do`
FortranDependency: make sure gfortran ends up in PATH 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 Homebrew/homebrew#38448. 2015-04-07 16:37:22 -07:00			`which(ENV["FC"] \|\| "gfortran")`
Add :fortran requirement 2013-06-23 18:35:20 -07:00			`end`
			`end`