In the next couple of weeks I will be trying to work on some of those issues. I think that eliminating external and fixing "openssl 1.0" issue are probably most pressing ones. I feel like we have gotten to the point where are some of these issues start hindering the development of the project.
Does anybody have suggestion in what sequence we should be proceeding? For example even though archaic openssl causes headache, is it actually necessary to build kernel or run unit tests? Should it be actually required in setup.py? Also recently I commited manifest_from_host.sh ( https://github.com/cloudius-systems/osv/blob/master/scripts/manifest_from_host.sh) script that I think can be helpful in this exercise to eliminate build from scratch in some of the modules by pulling artifacts from the host. Waldek On Sunday, March 31, 2019 at 5:02:11 PM UTC-4, rickp wrote: > > On Sun, 2019-03-31 at 11:54 -0700, Waldek Kozaczuk wrote: > > The second group's need should be addressed by Capstan. So we should > > avoid duplication between what Capstan does well (and hopefully will > > do even better in future) and OSv build system. Now capstan packages > > are often generated using osv-apps and OSv build system. > > As I've mentioned before - we're using a plugin I wrote to the erlang > build tool 'rebar3' which takes an erlang/OTP application and an OSv > base image and builts a unikernel image. > > The reason for this approach is the slightly complex nature of making > the image. We're emulating what the OSv build system does, using cpio > to push in the components to the file system over a tcp port. > > Is that what capstan does too? Or is there a simpler way that I've > missed? > > Rick > > -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osv-dev/2c913b5d-fb2d-4673-a471-697fda4e81ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
