On Thu, Apr 27, 2006 at 09:30:54AM -0700, Eric Wilhelm wrote:
- UC requires not only Perl, but lots of Perl modules. For example,
even on my Linux machine I still cannot run it because CPAN errors out when trying to install the needed stuff. So for UC to be usable, especially on Windows, we need to carry all this stuff packaged with
Please send me the error? OS/dist? perl --version ? I would be thrilled to help you fix it and maybe figure out how to avoid this on other systems.
Perl is really very cross-platform. CPAN has been around for over 10 years now and while CPAN.pm has some (internal) warts, it "Just Works" 99% of the time.
I'll point out that we had many similar sorts of issues with the python extensions. Folks had the motivation to get those smoothed out in order to use Inkscape extensions, and so it's working reasonably well now.
Many of the issues sound to be the normal issues that come with any new code; once there are enough people using it, things will get smoothed out.
Also, be aware that with Perl there are a lot of other kinds of ways to package modules. CPAN is generally considered the most convenient, but it's also possible to create and distribute "Bundles", or even "install" the modules into the package tree before tarballing and install them as part of the inkscape installation process.
Anyway, like Eric mentioned, Perl's been around on Windows for a long time, and the installation/packaging/portability techniques are well established.
I had hoped that the copy/paste install instructions would do the trick. I've only got a limited number of machines to smoke test on. As for windows, it is certainly possible to create a binary package with a frozen perl version and everything else.
Hmm, frozen binary packages sounds like overkill in this case. Do you rely on any C Perl modules?
Bryce