Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ProCoreBundle doesn't work well with Projeny #46

Open
ChuckSavage opened this issue Nov 20, 2016 · 5 comments
Open

ProCoreBundle doesn't work well with Projeny #46

ChuckSavage opened this issue Nov 20, 2016 · 5 comments

Comments

@ChuckSavage
Copy link

The asset ProCoreBundle, when unpacked is 6 more asset packages that Projeny doesn't recognize and add to the packages. So I copied them to the default unity folder. Then refreshed the projeny Releases list, and they now show up. But when I go to install them, after the first one, it gives me an error because they all want to be in the UnityAssets / ProCore folder, and then have separate sub-folders in ProCore. So now I cannot use them with my Projeny project, using the Releases window to install them.

@ChuckSavage
Copy link
Author

ChuckSavage commented Nov 20, 2016

Finding a solution, by renaming each one from ProCore to their proper name, ProBuilder, ProGrids, etc. Yet managing the entire bundle at once would be better, I think.

@svermeulen
Copy link
Contributor

svermeulen commented Nov 20, 2016

I'm not familiar with ProCoreBundle, but if they all want to be inside the ProCore folder, can't you just extract them all into the same projeny package?

Your solution to rename them to different projeny packages works too. Don't forget to set up package dependencies in that case though.

I don't know if there's a way to really automate this. In cases like this, my guess is you have to manually re-jigger things to make them work with projeny properly.

@ChuckSavage
Copy link
Author

The problem with this often you don't want all the packages of the bundle in every project.

@svermeulen
Copy link
Contributor

In that case then yeah, I would make them different packages. With their dependencies set up between each other using ProjenyPackage.yaml files

@luizcarlosfx
Copy link

I think it should be possible to move packages folder out of the root Assets folder. Why isn't it possible? I like to move all my exensions in a folder called "_Extensions", I also have two assets in the asset store and they both use the same root folder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants