Skip to content
This repository has been archived by the owner on Apr 11, 2024. It is now read-only.

Remove git-lfs? #70

Closed
li-bei opened this issue May 25, 2020 · 12 comments
Closed

Remove git-lfs? #70

li-bei opened this issue May 25, 2020 · 12 comments
Labels
question Further information is requested

Comments

@li-bei
Copy link
Contributor

li-bei commented May 25, 2020

I don't think enable git-lfs for an image which will almost never change and let users do some extra setups is worth.

How about just remove git-lfs?

cc @icodesign

@imWildCat
Copy link
Contributor

Can we refer to this image by dragging it into issues textarea then get the URL of this image?

@icodesign
Copy link
Contributor

I would say this is more of an Apple issue. I encountered it a lot when using other packages as well. Even we removed this file, there's no guarantee that we wouldn't add another file and it's not a good idea to ask contributors to stop using Git LFS (the right thing).

If you're going to use SPM, you're gonna face this issue until Apple fix it. Otherwise, Carthage/CocoaPods are still options.

I tend not to fix from our side as long as we've provided enough information.

@levinli303
Copy link
Member

Removing LFS might not be very viable, since it is already in the history. If there are devs who are trying to fetch an earlier version from Xcode, the same thing would still happen.

@levinli303 levinli303 added the question Further information is requested label May 26, 2020
@imWildCat
Copy link
Contributor

Another reference is that: ResearchKit does have git-lfs: https://github.com/researchkit/researchkit

@li-bei
Copy link
Contributor Author

li-bei commented May 26, 2020

It seems ResearchKit will ignore lfs files for clone and pull: https://github.com/ResearchKit/ResearchKit/blob/master/.lfsconfig

Looks like a nice solution.

@icodesign
Copy link
Contributor

TIL. That's decent.

@levinli303
Copy link
Member

I created a branch with this commit, however the issue did not get resolved when I was using Xcode to fetch it as a swift package (specifying the branch name as exclude-lfs-on-clone).

The difference that creating .lfsconfig excluding files makes is that it will prevent lfs files being resolved, but git-lfs will still get called, I think due to .gitattribute.

There might not be a way to work around this on machines without git-lfs.

@li-bei
Copy link
Contributor Author

li-bei commented May 27, 2020

@eyvallah I guess Xcode will clone all branches and check out to your specified branch, only one branch with .lfsconfig seems not enough.

@levinli303
Copy link
Member

Now I'm having no issue with the spm inside latest Xcode now even without the symbolic link hack, lfs files were simply not resolved and that is ideal. But I'm not sure if it works for everyone now.

@icodesign
Copy link
Contributor

I checked and still need the hack.
image

@icodesign
Copy link
Contributor

The error above is because that the script Apple is using doesn't include /usr/local/bin in its path while git-lfs is put under that path for most of us.

I think we can skip it since it's not an issue of this repo.

image

@levinli303
Copy link
Member

Let's close this for now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants