Move the plugins.json file to some more suitable location #26

Closed
AliSoftware opened this Issue May 21, 2014 · 6 comments

Comments

Projects
None yet
3 participants
@AliSoftware
Contributor

AliSoftware commented May 21, 2014

See CocoaPods/cocoapods.org#68 comment

Hosting it in cocoapods.org repo does not make much sense, and make it quite hidden.

Probably move the file to this cocoapods-plugins repo? or to CocoaPods/shared? or even CocoaPods/CocoaPods?

/cc @dbgrandi

@AliSoftware

This comment has been minimized.

Show comment Hide comment
@AliSoftware

AliSoftware May 22, 2014

Contributor

After some more discussion, let's keep it in cocoapods.org but move it to the root folder (and not in /data) so that it can be served by cocoapods.org

Contributor

AliSoftware commented May 22, 2014

After some more discussion, let's keep it in cocoapods.org but move it to the root folder (and not in /data) so that it can be served by cocoapods.org

@AliSoftware AliSoftware referenced this issue in CocoaPods/cocoapods.org May 22, 2014

Closed

Update the list of known plugins #68

3 of 3 tasks complete
@orta

This comment has been minimized.

Show comment Hide comment
@orta

orta May 22, 2014

Owner

👍

Owner

orta commented May 22, 2014

👍

@AliSoftware AliSoftware self-assigned this May 22, 2014

AliSoftware added a commit to CocoaPods/cocoapods.org that referenced this issue May 25, 2014

Moved plugins.json from 'data/' to root dir (see #68 and CocoaPods/co…
…coapods-plugins#26). Added a temporary symlink so that cocoapods-plugins keeps working until next release.
@AliSoftware

This comment has been minimized.

Show comment Hide comment
@AliSoftware

AliSoftware May 25, 2014

Contributor

Damn, using a symlink in data/plugins.json to point to plugins.json won't work, as cocoapods-plugins uses the raw.githubusercontent.com URL.

So for now I just duplicated plugins.json in root and in data/plugins.json.
The plugins.json in root is the new official reference, and the one in data/ will have to be removed in the future, once a new version of cocoapods-plugins will be released.

Contributor

AliSoftware commented May 25, 2014

Damn, using a symlink in data/plugins.json to point to plugins.json won't work, as cocoapods-plugins uses the raw.githubusercontent.com URL.

So for now I just duplicated plugins.json in root and in data/plugins.json.
The plugins.json in root is the new official reference, and the one in data/ will have to be removed in the future, once a new version of cocoapods-plugins will be released.

@AliSoftware

This comment has been minimized.

Show comment Hide comment
@AliSoftware

AliSoftware May 25, 2014

Contributor

@dbgrandi / @irrationalfab / @orta / @alloy may I be added to the owners of the RubyGem so I can rake release a new version that uses the new path?

Note that this 0.2.1 version also migrates to CLAide::Argument so requires that claide-0.7.0 is being released (and that a new patch version of CP that uses claide-0.7.0 is released too?)

Contributor

AliSoftware commented May 25, 2014

@dbgrandi / @irrationalfab / @orta / @alloy may I be added to the owners of the RubyGem so I can rake release a new version that uses the new path?

Note that this 0.2.1 version also migrates to CLAide::Argument so requires that claide-0.7.0 is being released (and that a new patch version of CP that uses claide-0.7.0 is released too?)

@fabiopelosin

This comment has been minimized.

Show comment Hide comment
@fabiopelosin

fabiopelosin May 26, 2014

Owner

@AliSoftware I think that you need to create a RubyGems account first:

gem owner --add olivier.halligon@gmail.com cocoapods-plugins
Removing olivier.halligon@gmail.com: Owner could not be found.
Owner

fabiopelosin commented May 26, 2014

@AliSoftware I think that you need to create a RubyGems account first:

gem owner --add olivier.halligon@gmail.com cocoapods-plugins
Removing olivier.halligon@gmail.com: Owner could not be found.
@AliSoftware

This comment has been minimized.

Show comment Hide comment
@AliSoftware

AliSoftware May 26, 2014

Contributor

@AliSoftware I think that you need to create a RubyGems account first:

@irrationalfab Done.

But again, wanting some support on my first gem release, especially as this one has some repercussions (we need to release claide-0.7.0 first, then release cocoapods gem so that it uses this new claide, then release cocoapods-[plugins|try|trunk]… I don't want to mess up everything)

Contributor

AliSoftware commented May 26, 2014

@AliSoftware I think that you need to create a RubyGems account first:

@irrationalfab Done.

But again, wanting some support on my first gem release, especially as this one has some repercussions (we need to release claide-0.7.0 first, then release cocoapods gem so that it uses this new claide, then release cocoapods-[plugins|try|trunk]… I don't want to mess up everything)

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