On 25 Oct 2012, at 11:48, Norbert Hartl <[email protected]> wrote:
> Am 25.10.2012 um 07:42 schrieb Sven Van Caekenberghe <[email protected]>: > >> Igor, Sean, >> >> On 25 Oct 2012, at 04:19, Igor Stasenko <[email protected]> wrote: >> >>> I have some: >>> - add tests to check if it works. So we will know if it functional or not >>> before people >>> will start using it and find by themselves :) >> >> I know that an older plug works, that is not the problem. >> >> Also, the tests are there: jenkins is building with all Zodiac tests passing. >> >> The questions are: >> >> - are we talking about the same vm ? >> - if so, why does it work on the build server and not for users ? >> > I partially answered that in a response to another mail of you. If it comes > to dynamic libs there is a source for failure. The library setup is not the > same for every e.g. linux. So the prerequisites are compiled into the library > but there is nothing to check at installation time. The vm is distributed in > a plain file archive and not in an installation package. Building package for > each platform could solve it :) I'm thinking since a longer time to package > the vm for me so my deployment time will be reduced. It isn't very hard to > build those packages. > > Norbert Hmm. it still feels as if it should be possible to build the SSL plugin in another environment. After all, the VM itself also has dynamic library dependencies that seems to work on multiple platforms without installers. If at all possible, we should try to keep the vm as simple as possible. Sven
