On Wed, 2018-03-21 at 21:48 -0500, Ted Gould wrote:
On 03/21/2018 07:43 PM, Martin Owens wrote:
I've separated out the extensions directory into a new repository:
https://gitlab.com/inkscape/extensions
I haven't yet removed the files from the master branch, but I will
as
soon as I get a couple of nods of approval from other developers
and
packagers as this change needs some consideration.
Yes, do you have a proposal for how all those things should work? Don't forget to worry about translations as well.
Yes.
The non-hard things is just translating to python3, I've found the test directory which has some serious problems, but have started rehab (one of which is it being called 'test' which conflicts with python's test module)
Once that part is done, we start making extensions a community thing, rather than a developer only thing.
Firstly we put any non-python extensions into their own repository. We don't want to drop support for just running weird shell scripts and perl stuff, but I'd put it in auxiliary and ask packagers to add them to separate packages.
This is so we can focus the core extensions repository on making it a python installable module set with the inx coming along as data.
The reason we'd want to move in this direction is really to allow inkscape to install and uninstall extensions while not having to write our own dependency software.
If we take advantage of pip/virtualenv in our .local/share/inkscape/extensions (Or do we stuff everything in .config like naughty XDG users 😉) then we can install extensions from zi p files, from git repositories on github and do uninstalls by just managing the pip repository from the inkscape UI.
This will install all the required dependencies (numpy anyone?) and keep files separated.
Just imagine being able to invite all those github repositoryinkscape extensions and inkscape.org zip file extensions into being used by Inkscape users. It'll be amazing.
Best Regards, Martin Owens