Home Download Buy Blog Forum Support

Best practices for plugin-deployment and packaging

Best practices for plugin-deployment and packaging

Postby chris.parnin on Tue Sep 17, 2013 11:16 pm

I've developed a plugin called autogit that will autocommit to a git repository on every file save.
https://github.com/chrisparnin/autogit/ ... autogit.py

This works great. But when I'm deploying this to other users, I'm wondering what is the best practice for packaging the plugin, especially when another python module (pygit2) and native libraries (libgit2) are involved?

Chris Parnin
http://blog.ninlabs.com
chris.parnin
 
Posts: 4
Joined: Tue Sep 17, 2013 10:54 pm

Re: Best practices for plugin-deployment and packaging

Postby sapphirehamster on Wed Sep 18, 2013 6:59 am

Most everyone uses Package Control to distribute plugins, and that takes care of packaging.

As for third-party packages, there's no real elegant solution AFAIK. Normally people just include them in the plugin directory and modify sys.path.
sapphirehamster
 
Posts: 88
Joined: Sun Jul 01, 2012 11:19 pm

Re: Best practices for plugin-deployment and packaging

Postby wbond on Thu Sep 19, 2013 3:45 pm

For a situation where you need to include code for specific platforms and architectures you can specify different packages for those, or you can create a single package with all of the files and choose the correct folder to add to sys.path by checking sublime.platform() and sublime.arch(). If you look at the SVN package I wrote, you'll see how I am handling _ssl.so for linux on different architectures and versions of Sublime Text.
wbond
 
Posts: 528
Joined: Mon Feb 28, 2011 5:33 am

Re: Best practices for plugin-deployment and packaging

Postby chris.parnin on Fri Sep 20, 2013 2:34 pm

Thanks. I was able to successfully set up things in package control.
chris.parnin
 
Posts: 4
Joined: Tue Sep 17, 2013 10:54 pm


Return to Plugin Development

Who is online

Users browsing this forum: Exabot [Bot], Google [Bot], mattst and 4 guests