-
Notifications
You must be signed in to change notification settings - Fork 52
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
Adding local repositories #81
Comments
Do you have installed a local git server? I think the url needs to point to a server, not just a repo. So you can keep the packages.plist local, but the repo needs to be on a server. |
This approach still works for me, but I don’t have an M1 equipped Mac, so maybe that is the difference. |
I actually managed to install a local repository. The {
packages = {
plugins = (
{
descriptions = {
en = "Dev Plugin 1";
};
path = "MyPluginInDevelopment.glyphsReporter";
url = "file:///Users/…/00 - Development/Glyphsapp-Plugins/my-plugin-repo";
},
);
};
} But that also just clones my local plugin files into Glyphs Repositories directory, so I am not sure if that improves anything. |
I wonder if that’s possible at all, I get my local repos to show up in the plugin manager, but Glyphs 3 crashes when trying to install.
First: The reason why I try that is, that the authorisation doesn’t even accept my own python plugins unless I "properly" install them. But this is not useful when developing, as I would have to re-install for every little change. My old approch with using aliases fails now. Even double clicking the plugin to install via Glyphs, which then recognises that it’s a Repo and asks if I want to use the Alias, eventually ends in the Notification that it’s from an unknown developer. Maybe you have a better idea of a python dev workflow, if so, the following might be obsolete.
Here’s my setup:
"my-dev-plugins.plist":
Then this "my-dev-plugins.plist" is added to Preferences > Addons > Alternate Plugin Repos
Then it shows in the Plugin Manager, but when clicking Install, Glyphs crashes with a system crash report that contains something about assertion failure in the git_clone command. This comes up only if I add a "/.git" to the url (just trying things):
I didn’t send the crash report yet, to not clutter your reports. I assume I already made a couple of mistakes in this setup.
If that approach is valid and useful for others (and we can fix my mistakes here) I am happy to draft a guide for others to use, as I think it’s very neat if that’s working.
The text was updated successfully, but these errors were encountered: