Hi OdyX, > Given the lack of proper NSIS releases, but given the improvements > made in their VCS, I think it would be nice to have a more recent > nsis, a snapshot from their SVN.
That's a good idea and it is also on my mind for sometime. However before I move onto that I would like to lay the foundation for it. This means spitting the NSIS package into smaller packages to reduce the load on the build servers for the different architectures and make sure installer packages can be build on any Debian architecture with NSIS. I thought about splitting the NSIS package into: * compiler and utils (architecture dependent) * plugins, stubs and resource files (architecture independent - win32) * plugin development kit (architecture independent - win32) * documentation and examples (architecture independent) Unfortunately there would be a circular dependency for running the tests during the package building. The NSIS compiler (makensis) would need the plugins, stubs and resource package during the test stage. So I am currently investigating how this issue could be solved best. Any suggestions in this matter are very welcome. Another advantage of the package splitting would be to have two sets of plugins/stubs packages for unicode and multibyte character support. Best regards, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
