Skip to content
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

Integration with LFS #4801

Closed
marchinram opened this issue Jan 21, 2016 · 10 comments
Closed

Integration with LFS #4801

marchinram opened this issue Jan 21, 2016 · 10 comments
Labels
s1:awaiting input Waiting for input from the original author t3:discussion These are issues that can be non-issues, and encompass best practices, or plans for the future.

Comments

@marchinram
Copy link

I have some large .a files stored in GitHub LFS and listed in my podspec as vendored_libraries. When I run pod install they do not get copied to my pod directory, am I doing something wrong or is this functionality not supported?

@segiddins
Copy link
Member

What needs to be done beyond git clone to download LFS stuff? Can you give us an example podspec we can investigate with?

@marchinram
Copy link
Author

It's an extension to git: https://git-lfs.github.com/?utm_source=github_site&utm_medium=blog&utm_campaign=gitlfs

I'm not really sure what is added haven't been able to figure out yet, will look into this. Unfortunately my podspec is for work and I cannot share, however the podspec was not changed at all to support lfs, it just adds a .gitattributes to describe which files are stored in lfs

@segiddins
Copy link
Member

Right but we need access to a repo setup however it has to be for LFS to determine what needs to be done in the CocoaPods downloader to support it.

@segiddins segiddins added t3:discussion These are issues that can be non-issues, and encompass best practices, or plans for the future. s1:awaiting input Waiting for input from the original author labels Jan 24, 2016
@srubin
Copy link

srubin commented Jan 29, 2016

As a point of reference: I'm using cocoapods with git-lfs and it's working fine. It would likely break if you didn't have git-lfs installed on the machine where you're pod installing.

@phatblat
Copy link

Just had a hangup with this for a vendored library. Turned out to be that CocoaPods had cached the library before Git LFS had been enabled (with git lfs install) on the build server.

The fix was easy, just delete the CocoaPods cache folder after enabling Git LFS, like so:
rm -rf /Users/$USER/Library/Caches/CocoaPods

@neonichu
Copy link
Member

neonichu commented May 1, 2016

Looks like as if there is nothing actionable for us to do here.

@neonichu neonichu closed this as completed May 1, 2016
@marner2
Copy link

marner2 commented Jul 28, 2017

We have a requirement to use a git lfs Pod Repository without running the command git lfs install (which modifies the global .gitconfig file and messes up another part of our pipeline). Can CocoaPods be modified to handle this? @neonichu

@phatblat
Copy link

@marner2 you can use an .lfsconfig file at the root of the repo without the need to touch the global .gitconfig.

@marner2
Copy link

marner2 commented Sep 5, 2017

@phatblat can you elaborate on this? I don't see how the .lfsconfig is supposed to help. That's for configuring specific options once git-lfs is already being used. That file has no effect if git lfs install hasn't been run and we don't have a way to call git lfs pull before things are copied to the Pods folder.

I'm not trying to change any git-lfs settings, I just want to make cocoapods download the git lfs files from a cold start (uncached) without modifying the global or user .gitconfig.

@mesibo
Copy link

mesibo commented Feb 25, 2019

We'd like to know the current status on this issue. We also have a pod for installing a large framework (800+ MB) and many users have faced the same issue as OP described. It would be great if there was a way to indicate LFS in podspecs so that LFS can be automatically installed before fetching the frameworks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s1:awaiting input Waiting for input from the original author t3:discussion These are issues that can be non-issues, and encompass best practices, or plans for the future.
Projects
None yet
Development

No branches or pull requests

7 participants