Re: ebeast: electron + beast

[Tim Janik <timj gnu org>]

Good to see that it works for you.

I'm pondering to integrate the electron app build into the regular build
process, i.e. essentially make beast depend on npm and everything required
for electron ebeast packaging is then fetched via npm.
Well except for v8pp, that is. We'll have to maintain a patched version it seems
[1].

So I'm pondering to:

a) Possibly include a v8pp copy into beast, to spare everyone the git submodule
hassle (I don't know why git didn't opt to handle submodules *transparently*).

b) Introduce a hard dependency on npm and package ebeast via electron-packager +
several other modules that npm fetches.

Feedback, comments?



On 22.02.2017 17:50, Stefan Westerfeld wrote:
> > Eeek, sorry, I ran into this a couple days ago, fixed it locally in Rapicorn and
> > totally forgot about it.
> > Just pull the fix from Rapicorn master now, you've diagnosed this correctly.
>
> Ok, now that I've rebuilt everything, ebeast console works as advertised.
>
>    Cu... Stefan

[1] Due to an unmerged patch:
        https://github.com/pmed/v8pp/issues/39#issuecomment-281151273
-- 
Yours sincerely,
Tim Janik

https://testbit.eu/timj/
Free software author.