Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Thought: Git (etc.) Integration

Discussion in 'Package Manager' started by Scott-Michaud, Nov 17, 2018.

  1. Scott-Michaud

    Scott-Michaud

    Joined:
    May 26, 2015
    Posts:
    18
    Just going to throw this thought out there. It is based on the following assumptions:
    • Unity is intending to mix the asset store into Packman
    • The ECS architecture is intended to carve up Unity for segments to be enabled, disabled, or replaced.
      • ie: Move everything except tools and a core Unity kernel (ECS manager, etc.) into user space.
    One of the pain points of dealing with both packages and asset store content is maintaining private forks.

    One way of getting around this is mandating that (at least Unity and clearly marked opt-in Asset Store) assets include a Git folder, or the equivalent from another source control system, and use branches or tags (whichever is more convenient) to signal releases. This way, end users can create their own branches and merge in upstream code (from Unity or the asset developers) as needed. Package manager would handle dependencies in some Unity equivalent of submodules, including whatever the downstream developers add to their own projects. (This might be difficult with multiple projects, but the hypothetical Packman should be able to handle copying folders where they need to be, checked out to the correct branch/tag/commit.)

    I'm being a bit hand-wavy because there's a lot of implementation details that really don't matter from the viewpoint of this semi-suggestion. The point is that package manager looks to be on the trajectory of "we want to turn our engine into a kernel with a bunch of default components" but long-term maintenance of external (Unity or Asset Store) user-space code has no (currently announced) plans.

    Also, it's entirely possible that Unity has something better than this already in the works, just not announced (or announced but I haven't seen it).

    Thoughts? Concerns? Requests for clarification?
     
    bgrz likes this.