-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building on CentOS #313
Building on CentOS #313
Conversation
As someone that doesn't use CentOS, and is not even much of a devops person, PRs like this are difficult to review. I'll probably ping you on any issues we get on these scripts, so I'd love any further help you can provide. I think eventually I'd like to setup some VMs for running QA checks on stuff like this before we release. /cc @jsh, author of the CentOS install script. |
@technoweenie Not a problem. Just let me know when you got an issue, and I'll see if I can help. CentOS is my primary OS of choice ;) So I'm definitely testing that! |
@technoweenie You'll have to forgive me relative lack of experience with go, but... Now that you've removed the symlink, how is this supposed to build now? on 47f7350,
which is the Centos 7.1.1503 (should be the easiest case) |
Gah, I should add this to the readme or contributing guide. Go projects expect you to clone the repository to
I just use |
Here's a great way to get started hacking on Git LFS, and really any Go project:
|
Well... Thank you for the hand holding, I needed it apparently... let me just So this brings me to the inevitable question now, what is the purpose/scope of these scripts? Because BEFORE, they had two features (intended or not)
But as I see it now, the only course of action is to Which makes lines 37-39 pointless (in their current state) So what do you want this to do now? |
You're right, the new setup is a bit of a regression. Getting this to actually work on Windows (no more symlinking) is worth it IMO. I would say option 1 is the primary goal of these scripts. |
On CentOS 6, it will download the rvm and install the latest stable ruby release Tested on a BARE MINIMUM CentOS 6.6/6.5 chroot with nothing but yum installed
Tested against a CentOS 5.11 chroot
Using go built on CentOS 6, CentOS 5 is able to build git-lfs It appears to work.
This no longer depends on my sf binaries for download, but I don't think anyone is going to accept the solution. While it is better, and includes all the RHEL patches, I am sure someone or EVERYONE will say "Its too complciated" etc..." Better find a simplier solution without all the patches
Simple patch to go src to build on CentOS 5 Cleaned up a little Remove prompt for ruby on Centos 7 Tested on CentOS 5.11, 6.6, 7.1.1503
4d36d6e
to
567032e
Compare
@technoweenie Ok, I have 1 working again. I went ahead add took your suggested optional step 4 and added a symlink myself. I guess whomever writes a similar windows script could do the same thing, but with a junction? Just guessing. At any rate, it all works now. |
The build script for CentOS could not build the man pages on CentOS 6 since ruby 2 is not available. However, there is a way to get ruby via the RVM. That has been added in so that CentOS 6 can build the man pages using this script
Getting golang on CentOS 5 isn't really a "supported" idea, but I looked into a number of work arounds and settled on the simplest one. I saw it mentioned in the comments and gave it a try. If you would rather say NO to CentOS 5, I can remove that, but I can also say that this will build and run git-lfs on a a CentOS 5 Machine (Tested on a 5.11 VM).
Also add the ability to use a currently cloned version of git-lfs, so it does not always clone into /tmp