<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">Hi,<br class=""><div class="gmail_quote"><div dir="ltr" class=""><div class=""><br class=""></div><div class="">Is there a documented future plan for adding ability to make a package having dependency to only a submodule of another package? </div><div class=""><br class=""></div><div class="">Some libraries may want to split their full API into logical components and provide a way to integrate them individually. As an example, the popular networking library <a href="https://github.com/AFNetworking/AFNetworking" target="_blank" class="">AFNetworking</a> has components like 'Serialization', 'Security', 'NSURLSession' and 'UIKit' in its podspec, and users can depend on just a particular component rather than depending on full API.</div><div class=""><br class=""></div><div class="">I'm pretty sure there will be need for that feature in future and you most probably talked about that before. I just want to know if there is an existing concrete architectural plan.</div><div class=""><br class=""></div><div class="">Best,</div></div></div></div></div></blockquote><br class=""></div><div>Yes, we plan it. If you open a ticket we’ll use that to track the feature.</div><br class=""></body></html>