aaron@...749... wrote:
ted@...11... wrote:
This is really nice. Aaron, one thing that we'd talked about in the past is starting to move twoards having a seperate package of scripts, to remove some dependencies from the base Inkscape package. So, you'd have "inkscape.rpm" and "inkscape-scripts-python.rpm" that you'd install (if you wanted).
As someone who is starting to write more scripts, do you have thoughts on this? Would you perhaps want to start such a package? Do any of the packagers out there have any thoughts?
I'd love to start a package, but I'm sure I wouldn't have a clue. I thought I read somewhere that Inkscape was leaning toward a CPAN-like setup perhaps an XML-RPC service. In some ways I think distributing a package of extensions doesn't fit well with the cause.
Thinking about how scripts should be distributed reminded me of a question I wanted to as a few days ago. Should there be or is there a search path for extensions? Could I for instance install my custom effect scripts and thier *.inx files into ~/.inkscape/extensions ?
Aaron Spike