Feedback Some feedback on Package Manager git support

Spent some time this week experimenting with making my own packages as git repos hosted on gitlab. Overall it is promising but there were a few pain areas that I just wanted to report my feedback on.

Project Structure:
currently your package folder has to be the root of your repository which makes it kind of awkward to develop. Ideally you will be developing your package inside of a Unity project so assuming you want that project to be in git as well the only solution is workarounds involving sub modules or sub trees. It works fine but I feel like there could be a more convenient solution

Versioning Support:
currently there is no official support for package versions or updating your packages. This is a pretty important feature. You can work around it by manually editing the json but I think this needs to be supported in the package manager ui

Dependencies:
this is by far the most glaring deficiency. there really needs to be a way to make git hosted packages dependent upon other git hosted packages.

I really like the idea of the package system and think this could be the future of unity assets, particularly open source ones distributed outside of the asset store so I hope you continue to work on custom package support.

 

Totally agree on those points (particularly hooking a package to a Git subdir would be excellent for a lot of reasons)
Recursive as it might sound.. maybe if those things get to a testable stage it would be possible to release a packaged version with updates to the package manager without having to jump Unity versions....?

 

I am wondering if you had any updates of those questions and also, if not, where would it be the right place to check that some of those questions have been addressed? Is there a good way to track down package-manager-related development?
I am thinking, specially, on the "project structure" part of the conversion, being able to hook to a subdir of a repo (rather than the root) would be extremely helpful for us. I can see how a lone dev might not have that much of an issue, but when several people develop a single package and they need a reference project for testing and the like it does get complicated (and there are no good solutions for that: two repos? messy, single repo + split? breaks down, soft links? need to be replicated by hand (particularly tricky in multiple dev platform setups) etc, etc)
So, assuming that one feature is still on the way, how could I check that it's made it without bugging you guys? ;D

 

On the release note of the new 2020 alpha, there is this line at the very end :

Package Manager: Added support for a Git package to be located in a repository sub-folder.

Any doc on that ?

 

Super cool, thanks !

Does that allow us to have dependencies of other subfolder as package dependencies ?

Like in the package.json of

https://github.com/user/repo.git?path=/packageA

can I have

https://github.com/user/repo.git?path=/packageB

And more importantly, is the "multiple version" (like all the unity package, having the versions available and being able to hit "update" if there is a newer version according to SemVer) support coming ? Is there an ETA on that ?

Thanks a lot !

 

Ok cool, because currently I have to manually add packages in order, or I get errors, which is pretty bad for users.

Really ? Isn't it already implemented ? Because it's how it works with all unity packages, and it would be really cool to have for us aswell
Maybe not the "select your version from all available", but at least being able to upgrade with a button on the package manager. Having to delete the lock and all that is extremely not user-friendly, and a normal thing to have for managing packages :/

 

Ok fair enough ! Having dependencies and upgrade is fine to me !

 

Ok, so I've been trying things today :

- On the input field "Add from git URL...", I cannot type "#" (but I can paste it).

- I made a github action file that will split a repo containing multiple packages to branches, that you can get with https://github.com/YourUserName/MainRepoName.git#PackageName and will also rename "Samples" to "Samples~" and "Documentation" to "Documentation~" so you work on your project with everything, but it's fine in the git packages
Your main repo need to be structured like this :

Code (CSharp):

1. MainRepo
2.   - Package1
3.   - Package2
4.   - ...

Here is the github action :

Code (Bash):

1. name: Create package branches
2. on:
3.   push:
4.     branches:
5.     - master
6.  
7. jobs:
8.   rename_samples:
9.     name: Create branches
10.     runs-on: ubuntu-latest
11.     steps:
12.       - uses: actions/checkout@v2
13.       - run: |
14.           for i in `ls -d */`; do
15.             git checkout master
16.             branch=${i::-1}
17.             if [ `git branch --list $branch` ]; then
18.               git branch -d $branch
19.             fi;
20.             git subtree split -P $branch -b $branch
21.             git checkout $branch
22.             git config --global user.name 'github-bot'
23.             git config --global user.email 'github-bot@users.noreply.github.com'
24.             if [[ -d "Samples" ]]; then
25.               git mv Samples Samples~
26.               rm -f Samples.meta
27.               git commit -am "rename: Samples => Samples~"
28.               git push -f -u origin $branch
29.             else
30.               echo "${i}Samples does not exist"
31.             fi
32.             if [[ -d "Documentation" ]]; then
33.               git mv Documentation Documentation~
34.               rm -f Documentation.meta
35.               git commit -am "rename: Documentation => Documentation~"
36.               git push -f -u origin $branch
37.             else
38.               echo "${i}Documentation does not exist"
39.             fi
40.           done;

It's probably not perfect, but it's fine for what I wanted ! (and way easier to work with than working in the Packages/ folder of unity

 

First, that's fantastic!
Second... is there a way to get that through updating the package manager itself? I could use this yesterday but won't be able to migrate our Unity to 2020 in, well, quite a while. It would be incredibly useful if stuff like this could be cherry picked!

 

+1
It'll be of great help, as most people will probably use 2019 for 1-2 more years

 

2020.1.0a21.2690, using an AZERTY keyboard, Win10

 

Is this something that is likely to happen?

 

That's great Can't wait for that!

 

Can someone on the team reply to this thread when 2019.3.4f1 is out?
I'd like to switch to it right away

 

It's out now, using the feature today

 

That is amazing! Thank you! <3

 

Is it possible to backported this to 2018.4 ?

 

That's AWESOME!
Does that supports symlink?
Let's say that I have a file in the root of the repo, and I use symlink for reference in some sub folders that I use as package folders. Would that work?