-
Notifications
You must be signed in to change notification settings - Fork 176
fallback to local homebrew formula metadata during migrate #379
Copy link
Copy link
Open
Labels
area: formula resolutionaliases, oldnames, taps, casks, and formula lookupaliases, oldnames, taps, casks, and formula lookuparea: migrationhomebrew migration and brewfile compatibilityhomebrew migration and brewfile compatibilitypriority: mediumnormal prioritynormal prioritystatus: acceptedvalid and ready for someone to work onvalid and ready for someone to work ontype: featurenew user-facing behavior or capabilitynew user-facing behavior or capability
Milestone
Description
Metadata
Metadata
Assignees
Labels
area: formula resolutionaliases, oldnames, taps, casks, and formula lookupaliases, oldnames, taps, casks, and formula lookuparea: migrationhomebrew migration and brewfile compatibilityhomebrew migration and brewfile compatibilitypriority: mediumnormal prioritynormal prioritystatus: acceptedvalid and ready for someone to work onvalid and ready for someone to work ontype: featurenew user-facing behavior or capabilitynew user-facing behavior or capability
zb migrate currently relies on the live homebrew formula api. that means locally installed formulas that brew still knows about, but the api no longer serves, get skipped.
example: #338, where fasd exists locally and brew info works, but zerobrew can't resolve it from the api.
we should consider a migrate-only fallback to local .brew/*.rb metadata from the installed cellar when the live api misses. this should not block the rest of migration if the local metadata still isn't usable.