On Sun, 2016-01-10 at 16:22 +0100, Eduard Braun wrote:
What does "prefer" mean in this context? Is this a strict limitation or could we still do it in case we lack a better solution?
They consider it broken. While it's unlikely inkscape would be thrown out (it's too damn useful); they are right to ask us for a single non-conflicting license for our packages.
Or would we have to somehow get scour packaged for every Distro out there? Then I doubt this would be a workable solution...
It should be available as python-scour on debian, if not then is /should/ be packaged and many packagers would help us get it packages for their system.
Either way we'd still need a way to include Scour in Mac/Windows builds which I assume complicates the whole process even more?
Of course, but it's not like we don't have other requirements included for windows and mac builds already. I'm not sure of the process, but maybe pip can be used to get the modules for those at build time.
Could you elaborate on that? How do we "make sure that scour is available" and what would be "the various repositories for developers"?
The first people to be effected will be developers. So making sure they can install it will be important. pip is a good candidate, but having it in our ppa would be very useful too.
Best Regards, Martin Owens