Search Unity

  1. Unity 2019.2 is now released.
    Dismiss Notice

A git package can be a dependency of another git package?

Discussion in 'Package Manager' started by yu_yang, Nov 8, 2019 at 2:32 AM.

  1. yu_yang

    yu_yang

    Joined:
    May 3, 2015
    Posts:
    17
  2. felipemunoz_unity

    felipemunoz_unity

    Unity Technologies

    Joined:
    Apr 5, 2019
    Posts:
    10
    Right now, only semver dependencies are allowed in a package manifest. So, you can only use:
    Code (CSharp):
    1. "com.yuyang.unity-extensions.common":"1.0.0"
    The expected workflow for this should be:
    1. Package A depends on published version of Package B
    2. You publish a new version of Package B
    3. You update Package A to use the new released version of B.
    4. You publish the new version of Package A

    Now, assuming that you are not using your own registry nor are publishing packages... A workaround I can think of would be to:
    1. Have Package A with no dependency on B (so that you can add that package without dependency resolution issues)
    2. Add B to your project manifest with the git url, so that the two packages end up in the project.

    I seem to have read somewhere about a user package that allowed using git dependencies in the package manifest, but I haven't been able to find which package that is.

    Git dependencies in packages is on our roadmap though, but there is no ETA yet as to when it will arrive.
     
    TheoSabattie likes this.
  3. johnsoncodehk

    johnsoncodehk

    Joined:
    Feb 19, 2016
    Posts:
    8
    Is it possible to release upm to github?
    I am glad to implement this feature.