-
-
Notifications
You must be signed in to change notification settings - Fork 11.4k
Conversation
# patch scripts to work with homebrew symlinking | ||
def patches | ||
[ | ||
"https://gist.github.com/erbmicha/5970803/raw", # env.sh patch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the other approach of just hardcoding the Homebrew path instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was designed to work for all symlinking, not just homebrew. This way Basho can use it in their build process for other products.
On Jul 13, 2013, at 9:50 AM, Adam Vandenberg [email protected] wrote:
In Library/Formula/riak.rb:
- option '32-bit'
patch scripts to work with homebrew symlinking
- def patches
- [
I like the other approach of just hardcoding the Homebrew path instead."https://gist.github.com/erbmicha/5970803/raw", # env.sh patch
—
Reply to this email directly or view it on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When they accept it upstream then we won't need a patch, but in the meantime, the approach used in the other riak 1.4.0 submission has a smaller footprint.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If by "they" you mean Basho, then you are correct, but I've been told that won't be until the next release and then the formula will be updated accordingly.
On Jul 13, 2013, at 12:04 PM, Adam Vandenberg [email protected] wrote:
In Library/Formula/riak.rb:
- option '32-bit'
patch scripts to work with homebrew symlinking
- def patches
- [
When they accept it upstream then we won't need a patch, but in the meantime, the approach used in the other riak 1.4.0 submission has a smaller footprint."https://gist.github.com/erbmicha/5970803/raw", # env.sh patch
—
Reply to this email directly or view it on GitHub.
I'm sure there's a good reason, but why are we installing binaries instead of building from source? |
I tried that route originally, but Basho distributes the binaries with a patched Erlang R15B01. That is a pain to replicate. Besides, this is a much faster install :) On Jul 13, 2013, at 1:51 PM, Misty De Meo [email protected] wrote:
|
url 'http://s3.amazonaws.com/downloads.basho.com/riak/1.3/1.3.1/osx/10.6/riak-1.3.1-osx-i386.tar.gz' | ||
version '1.3.1-i386' | ||
sha256 '1169ddcbc1a613c734f3df7350b416e84c667faaae73b647d2fa696aa45bc085' | ||
ohai "There is no pre-compiled 32-bit version anymore. Go to http://docs.basho.com/riak/latest/tutorials/installation/Installing-on-Mac-OS-X/#From-Source and compile from source." | ||
end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This conditional needs to be removed; it's not OK to print stuff in the DSL section of the formula, as that means it will be printed every time this formula is loaded on 32-bit systems. The depends_on :arch => :x86_64
tells Homebrew to print an appropriate warning and disallow installing on such platforms.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed. Sending a new pull request...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you cancel this pull request so I can send a new one? It won't let me send while this is open.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can force-push back to the same branch and the current pull request will be updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nevermind. I didn't realize that the pull request would update with subsequent commits to the files included. Neat :)
That's unfortunate. I really would rather not drop support for 32-bit Macs. |
removing the comment about 32-bit not being available per comment by @jacknagel
end | ||
|
||
prefix.install Dir['*'] | ||
rm Dir.glob("#{bin}/*.orig") # get rid of the patch backups before symlinking to bin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove files before installing.
removed conditional
So, my pull request is over at #21155. Is that what people want to go with? I can squash it into one commit if that would help. |
FWIW, the patching approach (this pull request) gives these warnings (?) for me:
|
I know, but they succeed. I tried a few different ways to generate the diffs that wouldn't result in those warnings, but everything did. They were generate by git. Interesting that if I use the same file with "patch" at the commandline there are no warnings. Whatever flags homebrew uses with "patch" must be generating them. On Jul 13, 2013, at 7:02 PM, David James [email protected] wrote:
|
Calling this a duplicate of #21155. |
No description provided.