[Issue 445] Unity Package Manager Distribution #475
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
To avoid .meta files there could be a unity-specific branch for this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this change, Unity devs can add this package to their project using the Unity Package Manager. In manifest.json, all that's needed to be added is:
"com.revenantx.litenetlib": "https://github.com/aaronchapin-tocaboca/LiteNetLib.git?path=/LiteNetLib#feature/unity-package-manager",With the url changing, obviously after this PR has been merged.
A drawback is that the project has to have Unity's .meta files in order to be linked properly, which will likely be annoying for non-Unity devs. So far I haven't found a way around this, but if anyone has a suggestion I'd be willing to try it out!
fixes #445