Backup brew tap

[satnami]

I think brew tap list would be needed in case I downloaded formula from third-party repositories like (GitHub).

[alichtman]

Yeah, this is a good call.

Changes should be made both in backup.py and reinstall.py

Want to open a PR?

[ashley-woodard]

I plan on looking at this sometime before June. In the meantime, I think its worth pointing out Homebrew Bundle let’s you specify taps, casks, and MAS apps on top of regular brew packages all in one file. This is the solution I’ll probably end up hacking together soon. I would be glad that I throw together a PR at some point but it may be a few weeks. Thoughts, comments, suggestions? Let me know. Cheers.

[alichtman]

Yep, I like that approach. It would be great if you submitted a PR. Looks like the command we should run is: $ brew bundler dump. Then maybe just move the file into the backup. And we can also remove the code that creates the “brew_list” file.

…

On Wed, Mar 6, 2019 at 11:34 AM Ashley Woodard ***@***.***> wrote: I plan on looking at this sometime before June. In the meantime, I think its worth pointing out Homebrew Bundle <https://github.com/Homebrew/homebrew-bundle> let’s you specify taps, casks, and MAS apps on top of regular brew packages all in one file. This is the solution I’ll probably end up hacking together soon. I would be glad that I throw together a PR at some point but it may be a few weeks. Thoughts, comments, suggestions? Let me know. Cheers. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#218 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATpW9bkP9-vpAkutS-0IiSklu6a9iQnNks5vT_wvgaJpZM4aUEo-> .

[satnami]

Sorry @alichtman I'm not that much in python, so I'll leave it to @ashley-woodard

[alichtman]

@ashley-woodard Any update on this?

[cocoonkid]

Yes please, that would be a great addition. If it weren't over my pay grade (yet) I'd do it myself.
Shallow Backup is the best tool out there! It deserves more love.

[WorkInProgress-Development]

Just wondering what the hold up is for merging #294?
Again, thanks for a wonderful tool.

[alichtman]

@WorkInProgress-Development It's difficult to find time to maintain open source projects, excel in my professional full-time dev job and do what I want with my personal life.

[WorkInProgress-Development]

I understand.
I was just wondering if there was anything that needed testing or something, because of "Good to go after this change." on the pull request.

Anyways, thank you for an amazing tool, and I hope I haven't been cruel.

[alichtman]

Nah, that wasn't directed harshly at you. Just something I've been thinking about a lot ever since I (unintentionally) stepped back from open source.

From a technical standpoint, #292 and #294 touch a lot of the same code are a difficult to merge since I'm anticipating merge conflicts / regressions, and don't particularly want to deal with them right now.

[alichtman]

@WorkInProgress-Development Done. Thanks for being patient.

[cocoonkid]

@alichtman Thanks for your commitment.