Hi Igor

As a „seasoned“ Linux user (8 years openSUSE – 3 years Fedora) I agree this would be the best pattern, especially as the RPMs automatically install any dependencies like UniConvertor (when specified as „Requires:“ in the rpm spec file) and UniConvertor would be kept up-to-date through the package manager.

But Windows users don’t think like this and don’t understand when separate programs need to be installed for full functionality. Perhaps the Inscape windows installer needs to be more intelligent and look for an existing UniConvertor installation before installing static libraries?


Best regards, Simon

 

Hi Simon!

But actually external installation of UniConvertor is the best pattern (like under Linux) because we are going to accelerate
UniConvertor development and provide short life cycles for versions (2-3 months). Now we are receiving bug reports from
Inkscape win32 users about 1.1.3 version and therefore we have prepared external variant with integration patch to resolve
issues. So external installation will allow users easy upgrade UniConvertor and keep up to date it. Also from 1.1.5 version
internal UniConvertor structure has a lot of native dependencies so built-in variant will not be easy way for maintenance.

Regards,

Igor Novikov
sK1 Project
http://sk1project.org