On Mon, May 20, 2019 at 6:48 PM Waldek Kozaczuk
wrote:
> 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
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.
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
I also think there are two audiences in this context we need to take into
account:
- OSv developers - people that build apps just to test stuff; typically
experienced with OSv build system and its limitations -> can find their way
around
- OSv users - people that build apps to
Hi!
I might be saying some nonsense, but...
On Sun, 31 Mar 2019 at 17:25, Nadav Har'El wrote:
> n Sun, Mar 31, 2019 at 5:58 PM Waldek Kozaczuk
> wrote:
>
>> Here is a list of things we should try to do:
>>
>
> I think there are two very different issues involved here, that don't
> really need
n Sun, Mar 31, 2019 at 5:58 PM Waldek Kozaczuk wrote:
> Here is a list of things we should try to do:
>
I think there are two very different issues involved here, that don't
really need the same solution:
The OSv kernel's makefile, and the "apps" build system.
>- Propose and define model
Here is a list of things we should try to do:
- Propose and define model app layout (Makefile, GET, ...) under
osv-apps
- Typically each app has GET shell script, Makefile and module.py:
- GET typically downloads ad puts source files into upstream
directory
