swatchbooker w/o pip install pillow

[luzpaz]

as per #45667

[bfontaine]

We don’t allow core formulae to depend on tap ones. If this is a mandatory requirement we must move this formula to the Python tap.

[DomT4]

It should be fine to vendor. We do so in mitmproxy without any obviously horrific problems. Possible the instruction to use pip in this formula previously is a relatively old relic.

[luzpaz]

how do i make the install block work ?

[MikeMcQuaid]

Check out ansible.rb, that should be helpful.

[luzpaz]

From Cookbook:

homebrew-pypi-poet can help you generate resource stanzas for the dependencies of your Python application

Will test this out

[luzpaz]

@DomT4 this is also a little out of my comfort zone. Would you be willing to assist ?

[bfontaine]

Wrap this line in a block and give it to the line above; it should look like this:

resource("Pillow").stage do
  system "python", *Language::Python.setup_install_args(libexec/"vendor")
end

Resource#stage takes either a directory or a block. In the former case it’ll unpack (read: uncompress) in it. In the latter it’ll create a temporary directory, cd and unpack in it, call the block, then cd back to where it was previously. Here we’re using a block so that unpacking the resource doesn’t mess with the buildpath.

This is what ansible.rb does except that it uses resources to access all resources instead of retrieving each resource with its name using resource("<name>").

[bfontaine]

Ping?

[luzpaz]

Help needed on this... please

[ilovezfs]

@lupaz Does this help

https://github.com/Homebrew/homebrew-core/blob/master/Formula/mitmproxy.rb#L215-L223

[apjanke]

Closing this due to inactivity/lack of response. If you'd still like to pursue this, feel free to respond to the previous comments/questions and re-open on the new homebrew/core repo.