Can't change package name for manually installed package (and other few questions)

[Ivo-Deus-Looplex]

Hi, we've been developing and using a package that we've been installing manually (by adding the repository link to Package Control instead of submitting it to Package Control Channel), and a few questions have cropped up that I don't seem to concise answers to, so figured to try my luck asking them here. Apologizes if it isn't the proper forum for this, but I appreciate any input regards these questions:

• Is it possible to edit/define a package name to a package that isn't published on the Package Control Channel?, I see that it takes the repository name by default, as long with the repository description, but would be there any way to redefine them to something else?
• Our install and update process have been considerably long (around 2 minutes without bottlenecks), and I've been assuming it's due to the project size to some extent (130Mb), but is it normal that installs and updates take this long?, any other tips regards mitigating this issue?
• I noticed that packages are updated every time ST is launched/relaunched, as long as _auto_upgradefrequency is set to 0, but a common happenstance in our workplace is just letting ST running as we work with it. Does packages update without requiring a ST restart?

Once again I apologize if this isn't the proper space for these questions, but any redirection or help would be welcome. Hope you all have a wonderful week!

[FichteFoll]

Apologizes if it isn't the proper forum for this, but I appreciate any input regards these questions

This is a fine place to be asking such question, imho, although there isn't as much activity on this project as there used to be. Apologies for the late reply.

Is it possible to edit/define a package name to a package that isn't published on the Package Control Channel?

Yes, by providing a custom repository.json file in the documented format. Using the JSON repository allows you to utilize the full package specification capabilities of Package Control, including multiple packages, dependencies, different package names, different release channels for ST versions, ST version and platform restrictions, etc. Instead of providing a URL to the Github repo in the "Add repository" command input, simply specify a URL or a local path to this JSON file.

I've been assuming it's due to the project size to some extent (130Mb), but is it normal that installs and updates take this long?

Sounds like it, tbh. PC doesn't perform extensive operation besides downloading meta data, downloading package data, unzipping and re-zipping package contents and that shouldn't take longer than it would normally on your machine.

Does packages update without requiring a ST restart?

No, you may also trigger updates manually via the Package Control: Upgrade/Override all Packages command but there is no automated update schedule after ST has been launched.