the warning "Git SSH URLs will NOT work for ..." is annoying

[gfx]

I use a private specs on our GitHub enterprise so I** have to** use Git SSH sources; cocoapods, however, produces warnings about it, stopping pod repo push with validation errors. Thus, I (and all the team members) always adds --allow-warnings in pod repo push.

I think it is too strict that a Git SSH URL is regarded as invalid by default. Can you please remove this warning, or make it just a notice instead of validation errors?

[alloy]

I agree that these should be a notice instead. Can you please create a PR for that?

[segiddins]

@alloy over in CocoaPods we have an issue for a --private lint option

[gfx]

I'd like to make a pull-request but rake spec fails (https://gist.github.com/gfx/97b9a198d142d9b202f6 ).

--private looks good; adding a DSL could be better, I guess.

[alloy]

@segiddins I tried to find the issue about --private but couldn’t easily find it. If it’s only about this warning, though, then I wonder if we shouldn’t just change it to a notice instead. The core of the message remains helpful, but shouldn’t be treated as a warning imo.

[alloy]

I don’t want anything in the spec itself about the spec-repo it’s supposedly from. It doesn’t describe anything about the library.

[segiddins]

@alloy see CocoaPods/CocoaPods#2682. I will (eventually) add a private mode to the validator that won't lint these things.

[segiddins]

@fabiopelosin disagree, since a spec should be valid no matter where it is stored.

[fabiopelosin]

I would rule out this possibility […]

Errata corrige: I wouldn't rule out this possibility so quickly, […].

I don't have a strong opinion.

@fabiopelosin disagree, since a spec should be valid no matter where it is stored.

The alternative that I described embodies more information in the Specification and, therefore, it makes easier to preserve the validation status independently from the repo where the Podspec is stored. It is unclear to me why the opposite would be case.

[alloy]

The validation is related to the repo the spec is pushed to nothing about the library itself. Adding an attribute for this leads to DSL creep and artificially imposes more restrictions, whereas we should let users do whatever they seem for their workflow.

[segiddins]

Closing as a duplicate of CocoaPods/CocoaPods#2682.