| Age | Commit message (Collapse) | Author |
|
Slightly loosens up the wording to make it less narrow and more
tolerant of wider usage. Relates to #34041 and #34039.
Closes #34042.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
|
|
We have an upstream signed binary available! Big big love to Mattias
for this.
This PR converts all the existing tuntap dependencies into
binary-friendly tuntap dependencies, and adds a tuntap dependency to
requirements to look for the kexts.
Closes #33894.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Creates a new requirement that dictates packages are unable to install due to requiring a signed kext to function.
Closes #33404.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Closes #32953.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
add :osxfuse symbolic dependency
add ConflictsWithFuseForOsx requirement for osxfuse/fuse4x/fuse4x-kext
Closes #31975.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is as Python bindings are not build in a way that can have
system or Homebrew Python used interchangeably.
|
|
Otherwise super will overwrite @env_proc with the default value.
|
|
The method signature of Dependency changed in
1fdf69b90382c43493a5f62f0020729289db6c70, however LD64Dependency was
missed in the update. This resulted in failures in merge_repeats(),
which creates many dependency objects using all three arguments.
|
|
|
|
|
|
|
|
- PythonDependency now implies Python 2.7
- PythonDependency now uses brewed Python for bottling
- Use double-quotes everywhere
Closes #27112.
|
|
|
|
|
|
|
|
|
|
Returning nil is in the contract of the Comparable module, and a future
version of Ruby will no longer hide this error.
|
|
This is so a e.g. brewed Python's modules can be found by superenv.
References #26229.
Closes #26197.
|
|
* Only set PYTHONPATH for Python 2.
* Set the Python binary for superenv.
References #24842.
Closes #26197.
Closes #26216.
Closes #26218.
Closes #26228.
|
|
Closes #26067.
|
|
Closes #24842.
|
|
The array elements here are individual arguments to exec, not a string
to pass to the shell; this only appeared to work. In reality, `opam
list` accepts "|" as valid argument, and the command works fine without
grepping the output.
|
|
|
|
make sure it doesn't actually point to something else
since sitecustomize.py is put in a location found by pypy,
it breaks pypy by setting sys.executable to a path that is definitely wrong,
and may not even exist.
Closes #24581.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
|
|
Fixes #24456.
|
|
|
|
Fixes #23837.
Fixes #23866.
|
|
|
|
Make it more consistent with other requirements.
|
|
Should be using minimum_mac_os_requirement.rb
|
|
Improve robustness of `PYTHONPATH` by first unsetting it (during
`satisfy`) so that the `PythonInstalled` can get the `python.version`
and so forth and then, after that, setting the `PYTHONPATH` to our
`global_site_packages`.
In the `python_helper` we append to the `PYTHONPATH` so if that var has
been set in a formula, it is respected.
Brew audit does no longer complain about setting the
`ENV['PYTHONPATH']`.
|
|
that live in the `libexec` dir of a `Cellar`.
|
|
If `depends_on :python => ['modulename', :optional]` then the generated
option is now `--with-python-modulename`, so that it is possible to
actually make depending on python modules optional.
Further, `brew options` becomes more meaningful.
|
|
When a formula `depends_on :python` *and* `depends_on :python3`
the `modify_build_environment` method sets the PYTHONPATH
and the Python 3.x requirement then fails because it finds
the sitecustomize.py from Python 2.x in the PYTHONPATH.
|
|
|
|
|
|
Fixes #22002.
|
|
On Unix, the path separator is ':', whereas on Windows,
it is ';'. This is the first of a series of patch to bring
macbrew's and winbrew's codebases closer together.
The main places the magic constant ':' was being used were:
- the $PATH environment variable
- CMAKE-related environment variables
- pkg-config related environment variables
Closes #21921.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
|
|
Up to now a brewed Python, even if not linked, was preferred over
and external Python, so that you had to completely `brew rm python`
to have a formula link against external (mostly system) Python.
From now on it is okay to `brew unlink python`.
|
|
|
|
|
|
|