**** BEGIN LOGGING AT Tue Jan 11 02:59:56 2022
Jan 11 07:45:51 <mckoan> good morning
Jan 11 08:35:29 <hmw[m]> good morining
Jan 11 09:17:12 <jeroen_> Is there a method to collect all recipes inheriting a certain class?
Jan 11 11:02:58 <mckoan> jeroen_: AFAIK no
Jan 11 11:32:13 <jeroen_> mckoan: thanks, I don't how to do that either :(
Jan 11 12:15:26 <rburton> jeroen_: bitbake-layers show-recipes -i classnme
Jan 11 12:19:14 <jeroen_> rburon: I doubt that will work in a recipe since bitbake holds a lock or something similiar..
Jan 11 12:19:46 <jeroen_> rburton: sorry mispelled your nick
Jan 11 12:20:08 <rburton> why would you want to do that in a recipe?
Jan 11 12:20:48 <rburton> what are you trying to do?
Jan 11 12:30:07 <jeroen_> mmm, I am trying to add nodejs packages in a decent way.. ;) So instead of using npm I switched to yarn, so you can at least download + verify and install in seperate tasks.. perhaps npm can do by now, this is 4 years old or so...
Jan 11 12:33:18 <jeroen_> At the moment all nodejs apps store all their dependecies under ${PN}/node_modules, which is rather insane, it takes more then 400MB for 3 apps..
Jan 11 12:34:38 <jeroen_> So what I had in mind is to make the dependencies shared / global, but then I need to know which recipes have node dependencies in the first place.
Jan 11 12:41:17 <jeroen_> so to answer your question, what I try to do is: for all recipes using yarn; install their dependencies to /usr/lib/node_modules [ unless alread installed ]
Jan 11 14:55:20 <jeroen_> rburton: any brilliant idea how to cope with that?
Jan 11 15:09:17 <rburton> write recipes for each of the dependencies :)
Jan 11 15:09:22 <rburton> (s/write/generate)
Jan 11 15:13:30 <jeroen_> yeah, thought of that, but the nodejs world seems to be insane, you will get 100k+ recipes because they have dependecies for everything _and_ versioned
Jan 11 15:21:44 <jeroen_> you would almost laugh at it, https://www.npmjs.com/package/isarray, crying instead...
**** ENDING LOGGING AT Wed Jan 12 02:59:57 2022