title: Swift Package with optional dependencies?
body: <p>I am curious how I might set up the following:</p>
  <ul>
  <li>Create a core Swift Package with some basic functionality.</li>
  <li>Have other optional packages that dovetail with the core package (directly related). Could be 10+ function blocks of functionality.</li>
  </ul>
  <p>So in a swift package, you hard-code in dependencies. I don't want that. To keep app size to a minimum and allowing developers to pick function blocks of code as they need, would one have a developer include the core package, and then other packages with specific functionality as they need - which somehow rely on the core package?</p>
  <p>Would you just add the core swift package and then each function block swift package?</p>
  <p>I am wondering how this could be set up to allow for flexibility for developers - keeping core function blocks separate so they would be pulled into a project as needed. Keeping things as simple as possible.</p>