**** BEGIN LOGGING AT Sun Apr 12 02:59:58 2015 Apr 12 12:09:15 thanks kergoth! :) (and sorry for the delay) Apr 12 17:26:19 How would I compile a package for my image, but not install it (while still being able to use the files)? Apr 12 17:28:27 During image build time i mean Apr 12 17:46:25 what do you mean by use the files? Apr 12 17:48:07 Well it's a build time dependency for a few recipes, but not a runtime dependency. Apr 12 17:49:02 if it's a build time dependency for thsoe recipes, then it should be in the DEPENDS for those recipes Apr 12 17:49:27 Right. However what I'm trying to figure out is how to keep it off of the rootfs. Apr 12 17:49:39 that doesn't make sense. Apr 12 17:50:16 a build time dep doesn't magically become a run time dep unless its explicitly added, or the automatic dep code added it, in which case it's truly required (e.g. the shlibs code will add a runtime dep on a package containing a library if a binary links against that library) Apr 12 17:50:17 It's a strange case. It's working with erlang releases. In which they copy the built portions of the erlang runtime they need as part of the build process. Apr 12 17:50:22 Then at runtime don't need erlang on the system at all Apr 12 17:50:45 so erlang needs to be compiled for target, have parts of its runtime copied by other recipes, but never installed on the rootfs Apr 12 17:51:03 still not seeing the problem. having eralnd in the DEPENDS of a recipe won't make erlang get installed when you install that recipe into the rootfs, unless something actually required it, as i said before Apr 12 17:51:28 DEPENDS is build time, RDEPENDS_ is runtime Apr 12 17:51:59 Ahh I'm getting what you mean. Where would the files be located at that point? sysroot? Apr 12 17:52:39 adding A to DEPENDS of B == making A's do_populate_sysroot task a dependency of B's do_configure Apr 12 17:52:43 so yes Apr 12 17:54:38 Ah okay. Might have to append then. The dependency recipe doesn't have anything for the populate_sysroot task. Apr 12 17:55:06 no Apr 12 17:55:16 every recipe has a do_populate_sysroot task Apr 12 17:55:18 as defined by the bbclasses Apr 12 17:55:27 which stages files from its do_install into the appropriate sysroot Apr 12 17:55:30 you don't have to do anything Apr 12 17:55:42 it sounds like you're trying to solve a problem that doesn't yet exist. Apr 12 17:56:04 Probably. That's why I asked. I wasn't aware that took place. Apr 12 17:56:59 my point was, go work on the actual recipes, and if you hit a problem, then try to solve that problem. don't worry about things being installed into your rootfs unless they're installed into your rootfs.. Apr 12 17:57:12 * kergoth shrugs Apr 12 17:57:44 Ah it was being installed, but that was just because I was in a hurry. Now trying to remove + use. Apr 12 17:57:49 But this has cleared things up quite a bit. Apr 12 17:58:48 Thanks for the insignts. Apr 12 17:58:51 np Apr 12 17:58:52 *insights rather Apr 12 18:00:00 if this recipe is including, building, and shipping its own erlang, that should probably be fixed to use the erlang in the erlang recipes, but beyond that just remove it in do_install if it's being installed and you don't want it installed, within a single recipe. once you switch to using erlang via DEPENDS, it won't be installed unless it's needed at runtime. Apr 12 18:01:27 yeah. well if i can find it in sysroot by removing it from the image requirements, and just keeping it in the recipe depends then that's great. Apr 12 18:02:09 It's an odd build process, but it just naturally builds releases that only ship with only what it needs. Will save me a good 15MB or so. Worth the effort. Apr 13 01:55:04 wassssssssup **** ENDING LOGGING AT Mon Apr 13 03:00:00 2015