On 2017-06-07 13:43, Alexander Kanavin wrote: > On 06/06/2017 06:14 PM, Jan Kiszka wrote: > >> Yeah, good points. Probably this problem is also related to OE >> reimplementing parts of the npm logic. >> >> But I suppose those concepts won't materialize very soon, will they? I'm >> also looking for a short-term solution, at least some reasonable tactic >> to generate such recipes in the meantime. Is there something in that >> thread I should dig into? > > What I am getting at is that it would be awesome if you convince your > management that npm support in Yocto is a problem that needs a better > solution and work on it. Yes, this means you can't work on product > development for quite some time; this is the price for using open source > projects without a commercial support contract :)
We are such a instance support :) - but we also need to get paid / pay our contractors. > > My apologies if this is not the answer you were seeking. > I'm getting your point, even more now as I ran into a package that does not even install at all (node-red-contrib-opcua). Can't promise anything at this point, but I will carry this forward, in all directions. Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
