Issue 30 in google-js-test: Tag releases or update mac homebrew installation instructions

13 views
Skip to first unread message

google-...@googlecode.com

unread,
Jun 20, 2013, 2:29:06 AM6/20/13
to google-...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 30 by ori...@gmail.com: Tag releases or update mac homebrew
installation instructions
http://code.google.com/p/google-js-test/issues/detail?id=30

What steps will reproduce the problem?
1. homebrew google-js-test
2. no formula found

A few months ago, Homebrew separated projects without tagged version
releases to a different non-default "tap":
https://github.com/Homebrew/homebrew-headonly

Installing from this tap is a little more complicated.

Some possible approaches:
* update the homebrew installation instructions to:
** brew tap homebrew/headonly
** brew install --HEAD re2
** brew install --HEAD google-js-test
* tag versioned releases and have Homebrew move the formulae back to the
Homebrew core

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

google-...@googlecode.com

unread,
Jun 20, 2013, 8:00:13 PM6/20/13
to google-...@googlegroups.com

Comment #1 on issue 30 by jaco...@google.com: Tag releases or update mac
Thanks for the report.

Could you help with some context on the homebrew change? gjstest has tags in
its git repo and it has stable tarballs, and the latter was used in the
homebrew formula, complete with a hash to confirm it hadn't changed.

So I'm confused what the requirements are. Is there documentation somewhere?
The README on the link in your post doesn't explain what it means to be
head-only and how you escape that ghetto.

Jacob Wan

unread,
Jul 3, 2013, 1:44:15 PM7/3/13
to google-...@googlegroups.com, codesite...@google.com, google-...@googlecode.com
I think the issue was with its re2 dependency, as I guess re2 isn't tagged.  Here's a Github issue I created on the Homebrew repo:

google-...@googlecode.com

unread,
Jul 3, 2013, 7:10:57 PM7/3/13
to google-...@googlegroups.com

Comment #2 on issue 30 by jaco...@google.com: Tag releases or update mac
Thanks. I'm happy to do the work lifting gjstest back into the main repo if
somebody is willing to file and push through an issue on the re2 end? :-)

google-...@googlecode.com

unread,
Jul 3, 2013, 7:18:39 PM7/3/13
to google-...@googlegroups.com

Comment #3 on issue 30 by jaco...@google.com: Tag releases or update mac
Oops, that looked weird didn't it? I was replying to an off-list mail that
said the problem was with the re2 dependency, since re2 has no tags.

google-...@googlecode.com

unread,
Jul 3, 2013, 9:45:12 PM7/3/13
to google-...@googlegroups.com

Comment #4 on issue 30 by ja...@wildlemur.com: Tag releases or update mac
That was me. I'd left a note about the re2 issue over in a Google group
thread, and I guess it automatically cross-posted here. In any case, I
went ahead and created an issue on the re2 project:

https://code.google.com/p/re2/issues/detail?id=86
Reply all
Reply to author
Forward
0 new messages