Closed mootari closed 9 years ago
Could you provide a sample failing Brewfile
? Thanks!
Sure! I've provided multiple samples here: https://gist.github.com/cisso/ccadc42b4133d810d212 The one I mentioned above is Brewfile_fails_for_all_1.
Edit: Assuming that "Dsl" stands for domain-specific language, shouldn't that class merely parse/tokenize the Brewfile and return a list of sanitized Entry objects, so that they can be processed by a different class? (again, not a ruby guy)
This issue is related to the legacy codes here. Instead of raising the error when dealing with invalid Brewfile
, it tries to treat each line as individual formula name. In the result, some weird messages get out.
Should we just drop these legacy codes? cc @andrew
Yeah I'm not attached to the legacy code at all!
So, to be clear, what was the reason for requiring quotes in formula names inside of Brewfiles?
@kevinSuttle It's a Ruby DSL which means we don't need to implement our own parser.
@mikemcquaid Ok. So, not wanting to derail here, but that does directly affect Homebrew formulae, especially Caskroom.
@kevinSuttle I doesn't affect anything outside of Brewfile
s.
Currently the DSL seems to choke on invalid quotes, causing the whole Brewfile to fail with "missing formula" errors for each single line. I would suggest to either
I'm not a ruby guy and I've only briefly looked at the code, but my guess would be that the first option is actually easier to implement.