**** BEGIN LOGGING AT Sat Apr 27 02:59:56 2019
Apr 27 10:30:29 <BCMM> what exactly can i share between different build directories, to save time? for example, can i just symlink downloads/?
Apr 27 10:35:08 <yann> BCMM: sstate-cache too
Apr 27 10:35:39 <yann> depends on the archs you're attempting to share things for
Apr 27 11:01:24 <BCMM> yann: probably trying to share between raspberrypi and raspberrypi3
Apr 27 11:01:32 <BCMM> yann: what *is* sstate-cache?
Apr 27 11:02:39 <yann> BCMM: it's a cache of build artifacts
Apr 27 11:03:17 <BCMM> yann: meaning what? binaries and so on?
Apr 27 11:04:07 <yann> yes - if you're sharing between 32bit and 64bit arm platforms, you can't hope to share much more than host binaries
Apr 27 11:08:19 <BCMM> well that would be a good start
Apr 27 11:08:32 <BCMM> yann: so it would never be actually *harmful* to share sstate-cache, then?
Apr 27 11:08:49 <yann> I think so
Apr 27 11:09:05 <BCMM> i'll give that a try; thanks
Apr 27 11:09:16 <yann> that's what I'm doing myself anyway :)
Apr 27 11:10:07 <yann> I only switch sstate-cache on major changes that trigger near-full rebuilds
Apr 27 14:34:57 <yann> how can util-linux-script, util-linux-scriptreplay, and probably others creep into an image, when --graphviz does not show them ?
Apr 27 14:35:34 <yann> could that come eg. from something IMAGE_FEATURES ?
Apr 27 14:37:10 <yann> that's a bit unfortunate, as those are not alternative-managed and conflict with busybox applets :)
Apr 27 16:00:44 <justanotherboy> yann: It might be because of RDEPENDS or RRECOMMENDS of an installed package
Apr 27 16:01:02 <justanotherboy> yann: What are the conflicts with busybox?
Apr 27 22:10:27 <yann> justanotherboy: busybox postinstall fails because /usr/bin/script and scriptreplay are not symlinks - that is, because those binaries are not managed as alternative in util-linux
Apr 27 22:11:06 <yann> justanotherboy: and if they were simply in RDEPENDS/RRECOMMENDS, they would appear in the --graphviz output
**** ENDING LOGGING AT Sun Apr 28 02:59:57 2019