Writing a custom download strategy from scratch?

[lmartinez-mirror]

Hi, I'm looking into creating a cask for a program that only distributes binaries through Mega.nz. I thought about processing the package elsewhere in a build step, but I figured it'd be best to use a custom download strategy. My only question is, will I need to write it from scratch, and if so, are there any examples I can follow? The only requirement is core/megatools.

[jonchang]

Check out https://rubydoc.brew.sh/AbstractFileDownloadStrategy.html and its subclasses. Mostly what you'd need to do is properly implement fetch by using cached_location, symlink_location, and temporary_path correctly. Note that this would likely not be accepted into Homebrew itself, so you'd have to host this cask or formula in your own tap: https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap

[lmartinez-mirror]

Thank you so much! Does this implementation need to be in the same cask file or separate?

[gromgit]

It can be a separate library file. See my FUSE tap for how I accomplished a similar task (new requirement): https://github.com/gromgit/homebrew-fuse

[jonchang]

It can be in the same file or a separate file, but if it's a separate file you'll need to include the other file with something like require "../lib/megatools_download_strategy.rb"