Port `local git repos` feature from Bundler #1010

Closed
fabiopelosin opened this Issue Apr 29, 2013 · 7 comments

Comments

Projects
None yet
4 participants
@fabiopelosin
Member

fabiopelosin commented Apr 29, 2013

See Local git repos in this link.

Previous discussion at CocoaPods/Core#14.

@supermarin

This comment has been minimized.

Show comment Hide comment
@supermarin

supermarin Apr 29, 2013

Member

👍 👍

Member

supermarin commented Apr 29, 2013

👍 👍

@supermarin

This comment has been minimized.

Show comment Hide comment
@supermarin

supermarin May 6, 2013

Member

@irrationalfab should this be a part of Core?

Member

supermarin commented May 6, 2013

@irrationalfab should this be a part of Core?

@fabiopelosin

This comment has been minimized.

Show comment Hide comment
@fabiopelosin

fabiopelosin May 6, 2013

Member

Mhmm, tough cookie. I think that the configuration (being a model) file should be in Core and that the rest of the logic should be in the Installer. Moreover I think that the configuration file should be a simple YAML.

Member

fabiopelosin commented May 6, 2013

Mhmm, tough cookie. I think that the configuration (being a model) file should be in Core and that the rest of the logic should be in the Installer. Moreover I think that the configuration file should be a simple YAML.

@ghost ghost assigned supermarin May 8, 2013

@supermarin

This comment has been minimized.

Show comment Hide comment
@supermarin

supermarin May 10, 2013

Member

+1, the bundler's format is something not so common :)

Member

supermarin commented May 10, 2013

+1, the bundler's format is something not so common :)

@fabiopelosin fabiopelosin referenced this issue in CocoaPods/cocoapods-downloader May 31, 2013

Closed

Support for path downloading #2

@fabiopelosin

This comment has been minimized.

Show comment Hide comment
@fabiopelosin

fabiopelosin Aug 9, 2013

Member

After giving more thought to it I think that the best solution would be to adopt an approach similar to bundler as illustrated in previous post with some more adaptations for CocoaPods. CocoaPods differs from Bundler because it stores the dependencies per project instead of having a central storage.

I think that it would be really cool to have a dedicated command like:

$ pod edit [NAME]

This command could create a checkout of the source of the Pod in a dedicated folder (like Pods/Development/NAME) and could support a --submodule option to add it as a submodule. If the folder is present for a user CocoaPods should check that the user is using the last commit or a newer (and in that case it should update the reference SHA). If the folder is not present CocoaPods should checkout the reference SHA (in the Pods folder as ti would normally do) during the installation.

There should be also a command to stop editing the Pod.

$ pod no-edit [NAME]

To keep things simple I would remain focused on Pods sourced from git repos.

Member

fabiopelosin commented Aug 9, 2013

After giving more thought to it I think that the best solution would be to adopt an approach similar to bundler as illustrated in previous post with some more adaptations for CocoaPods. CocoaPods differs from Bundler because it stores the dependencies per project instead of having a central storage.

I think that it would be really cool to have a dedicated command like:

$ pod edit [NAME]

This command could create a checkout of the source of the Pod in a dedicated folder (like Pods/Development/NAME) and could support a --submodule option to add it as a submodule. If the folder is present for a user CocoaPods should check that the user is using the last commit or a newer (and in that case it should update the reference SHA). If the folder is not present CocoaPods should checkout the reference SHA (in the Pods folder as ti would normally do) during the installation.

There should be also a command to stop editing the Pod.

$ pod no-edit [NAME]

To keep things simple I would remain focused on Pods sourced from git repos.

@zakdances

This comment has been minimized.

Show comment Hide comment
@zakdances

zakdances Aug 20, 2013

That would be great. And "editable" mode with an optional --submodule tag would be incredibly useful

That would be great. And "editable" mode with an optional --submodule tag would be incredibly useful

jzapater pushed a commit to jzapater/CocoaPods that referenced this issue Sep 17, 2013

Merge pull request #1010 from tonyzonghui/master
[New Pod] UIImage-Categories
@segiddins

This comment has been minimized.

Show comment Hide comment
@segiddins

segiddins Jul 6, 2015

Member

Closing in favor of #2672.

Member

segiddins commented Jul 6, 2015

Closing in favor of #2672.

@segiddins segiddins closed this Jul 6, 2015

@orta orta referenced this issue Jul 4, 2016

Closed

Permanent development pods #5591

1 of 1 task complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment