If you use this procedure to remove a package that you installed from a registry, the operation removes the package from the current project.More info See in Glossary packages that you downloaded and imported, see Remove imported assets from a project. Offers a wide variety of assets, from textures, models and animations to whole project examples, tutorials and Editor extensions.
For information about removing Asset Store A growing library of free and commercial assets created by Unity and members of the community. Don’t use this procedure to attempt to remove packages that you imported to your project, such as an Asset Store package that you downloaded and imported.
For more information, including an illustrated comparison, see Show Dependencies. For example, the Show Dependencies setting is disabled by default, so packages that are installed as indirect dependencies don’t appear until you enable this setting. The package itself and all its functionality is still installed in your project, even though it might not appear in the In Project list context. If another installed package or an installed feature set depends on the package you are trying to remove, this procedure removes only the dependency from your project manifest.For more information about direct and indirect dependencies, see Dependency and resolution. If there are no other packages or feature sets that have a dependency on this package, any Editor or run-time functionality that it implemented is no longer available in your project.The result of removing the direct dependency varies, based on the dependencies for the package you are removing: The Package Manager uses it to configure many things, including a list of dependencies for that project, as well as any package repository to query for packages. This file must be available in the /Packages directory. More info See in Glossary from your project manifest Each Unity project has a project manifest, which acts as an entry point for the Package Manager. For projects, these are considered direct dependencies for packages, these are indirect, or transitive, dependencies. Projects and packages use the dependencies attribute in their manifests to define the set of packages they require. So if after uninstalling all editions of Unity you are looking to ensure that’s all been cleaned up and scrapped too, go to the command prompt and “cd %localappdata%\unity” and see what’s left behind.When you “remove” a package from your project, the Package Manager is actually removing the project’s direct dependency In the context of the Package Manager, a dependency is a specific package version (expressed in the form that a project or another package requires in order to work. Unity itself is a little different - if you installed the Unity hub, you can manage your installation files from there and get it all uninstalled neatly, but you may still have a ‘cache’ of downloaded packages hogging your machine and user’s local appdata folders.īecause I don’t even like that cache hogging my C “system” drive and don’t get a choice for where to put it, I created a junction for it - otherwise it can grow until it eats the drive (annoyingly). It doesn’t leave any other clutter around, really.
If you don’t want to get rid of the repo just yet, delete the rest except for that. git (sub) folder resides, that will also remove the git repository you pulled down from GitHub too. Unity projects are contained within their folder so to delete one, just remove the folder it is in.