Bug 854769

Summary:	Mountain Lion and git issues on Getting Started page
Product:	OKD	Reporter:	Sumana Annam <sannam>
Component:	Website	Assignee:	Sumana Annam <sannam>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.x	CC:	jofernan, libra-bugs, mmccomas, xtian, yujzhang
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-06 18:49:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sumana Annam 2012-09-05 23:08:53 UTC

Description of problem:

Followed the instructions from "Getting started" Mac section for setting up my Mac environment and ran into few hurdles on Mountain Lion 10.8.

1) The "git for OS X" URL link we point to, does not have DMG for 10.8
2) Also just installing XCode wouldn't be sufficient, one needs to install optional components called "command line tools" which bring in git. I am not sure whether this was always true but it is for Xcode 4.4.1.

Either way, IMO we should clarify this in our "Getting Started" Mac instructions.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Clayton Coleman 2012-09-07 17:50:51 UTC

You should have access to change this - please jump in and alter the text!

Comment 2 Sumana Annam 2012-09-19 23:10:15 UTC

Decided to do a KB instead;

link: https://openshift.redhat.com/community/kb/kb-e1068-git-installation-issues-on-mountain-lion-os-x-108

Comment 3 Xiaoli Tian 2012-09-21 05:14:43 UTC

Move it to ON_QA then since the KB is on PROD now

Comment 4 Yujie Zhang 2012-09-21 06:15:04 UTC

(In reply to comment #2)
hi Sumana, thanks for adding this KB page, I will verify this bug now.