I screwed up the branch I was originally going to send this from, so instead it's coming from a third branch. Anyway, differences between this and #16248 include:
New branch for my brew-run-configure.sh script because I screwed up m…
…y last one
- add brew-run-configure.sh
- add some directories for testing it in
Maintainers: is this something we want or not?
Remind me what this does?
It's basically an expansion on brew diy to make installing stuff into Homebrew's Cellar easier
Could/should this be part of brew diy? I don't see a harm in having it in Contributions regardless.
well if this were added to brew diy itself, it'd have to be rewritten in Ruby, and I don't know Ruby, so someone else would have to do that
Being very stupid here but can you explain what this does that diy doesnt? I'm just wondering if we want two similar commands written in different languages.
(An aside: I didn't know Ruby before contributing to Homebrew either. I now have a job writing Ruby.)
brew diy just tells you the configure flag to pass to ./configure, this script actually applies that flag for you and runs it.
Yeh, in that case I think this should be an argument e.g. brew diy --configure.
brew diy --configure
What are these gitignore files for?
To keep the directories from being empty.
If another maintainer wants this include, please work towards inclusion; otherwise I recommend it be a small project external to Homebrew itself. I'll close in a couple days unless another maintainer steps in.
I'm -1 on this as-is.
Passing on this for inclusion in core, but would link it from the wiki: https://github.com/mxcl/homebrew/wiki/External-Commands