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

Rome upload does not accept repository name (if differs from framework name) #30

Closed
erichoracek opened this issue Oct 7, 2016 · 5 comments

Comments

@erichoracek
Copy link

Current behavior

Cartfile:

github "bitstadium/HockeySDK-iOS"

Romefile:

[RepositoryMap]
    HockeySDK-iOS = HockeySDK

When building with Carthage:

$ carthage build HockeySDK-iOS --platform ios
*** Building scheme "HockeySDK Framework" in HockeySDK.xcodeproj

The following is produced: Cartage/Build/iOS/HockeySDK.framework*

However, unlike Carthage, the repo name does not work when passed to rome upload

$ rome upload HockeySDK-iOS
(nothing uploaded)

If the Framework name is specified, it does work:

$ rome upload HockeySDK
Successfully uploaded HockeySDK to: HockeySDK/HockeySDK.framework-4.1.2.zip
Successfully uploaded HockeySDK.dSYM to: HockeySDK/HockeySDK.framework.dSYM-4.1.2.zip

As such, rome upload doesn't function the same way as Carthage, which is what users would expect in this scenario (repository names are provided, not framework names)

Expected behavior

The upload command should take repository names, not framework names.

Rome version: 0.6.0.10
OS macOS sierra 10.12

@tmspzz
Copy link
Owner

tmspzz commented Oct 7, 2016

@erichoracek How would this play with the multiple aliases?

[RepositoryMap]
    awesome-cats = Caturday, CatCore

I assumed that one might want to upload just CatCore and not Caturday

@erichoracek
Copy link
Author

erichoracek commented Oct 7, 2016

@blender Since there is no way to tell Carthage to only build a single framework from a repository, I'm not sure this should be the default behavior. From your hypothetical example, invoking carthage build would produce both Caturday and CatCore. I can't think of a scenario in which you wouldn't want to cache both of these products. Even if there is one, perhaps it should be an additional parameter, e.g.:

rome upload --framework Caturday

But the default would still be:

rome upload awesome-cats

Which would upload both Caturday and CatCore.

@tmspzz
Copy link
Owner

tmspzz commented Oct 8, 2016

@erichoracek Thanks for you input. I'll need some time to think about what impact this has on the existing code/logic.

@tmspzz
Copy link
Owner

tmspzz commented Oct 8, 2016

@erichoracek please try pre-release v0.7.0.12

@erichoracek
Copy link
Author

Appears to be working, thanks!

@tmspzz tmspzz closed this as completed Oct 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants