**** BEGIN LOGGING AT Mon Jan 23 03:00:00 2017
Jan 23 09:51:10 <Jin^eLD> morning
Jan 23 11:13:16 <Crofton|work> rpm-native depends on which, or it fork bombs ....
Jan 23 11:13:24 <Crofton|work> welcome to my weekend
Jan 23 14:52:05 <LetoThe2nd> does anybody know the situation that a filesystem is mounted RO, and a directory residing on that filesystem gets bind-mounted to somewhere else, and later remounted RW?
Jan 23 14:52:36 <LetoThe2nd> $coworker says this used to work fine, and now hit some situation where this bind-only-remount does not work anymore, just rw-remounting the whole filesystem.
Jan 23 16:46:09 <abelloni_> So, I've been asked what would be the benefit of using oe-core instead of poky/meta (i.e. using pokay and removing meta-poky and meta-yocto-bsp)
Jan 23 16:46:20 <abelloni_> any input? :)
Jan 23 16:46:33 <rburton> abelloni_: you own the distro, instead of hoping that poky doesn't do something you don't want
Jan 23 16:47:01 <rburton> the short version is that poky is basically oe-core defaults plus a few tweaks, so you might as well - and are positively encouraged - to make your own distro
Jan 23 16:47:35 <rburton> you can still either use the poky repo (and just remove meta-poky meta-yocto-bsp from your layers) or change to fetching bitbake and oe-core separately
Jan 23 16:50:32 <abelloni_> rburton: yes, clearly, poky is out of the discussion, really the question was related to your last sentence
Jan 23 16:51:14 <rburton> if you clone both you need to be sure that you track them both
Jan 23 16:51:26 <rburton> ie there may be a commit to oe-core that depends on recent changes in bitbake
Jan 23 16:51:38 <rburton> but that's fairly trivial
Jan 23 16:52:40 <kergoth> and remember to track the correct bitbake branch/version for the oe-core branch in quesiton, since they use different naming schemes
Jan 23 16:52:49 <kergoth> master is easy, of ocurse
Jan 23 16:53:24 <abelloni_> kergoth: the question being how does one know which combination is working? :)
Jan 23 16:54:08 <kergoth> there's a wiki page, and oe-core's sanity.conf defines the required bitbake version, or you can check the poky repo
Jan 23 16:54:13 <joshuagl> https://wiki.yoctoproject.org/wiki/Releases
Jan 23 16:54:19 <kergoth> thanks joshuagl :)
Jan 23 16:54:37 <joshuagl> np, had just tabbed away to the browser and was about to type the same thing
Jan 23 16:54:43 <joshuagl> you saved me half a job kergoth 
Jan 23 16:54:49 <kergoth> :)
Jan 23 16:55:22 <kergoth> sanity.conf is pretty definitive, if you're paranoid, but any should do :)
Jan 23 16:57:23 <abelloni_> sure but I'd argue that https://wiki.yoctoproject.org/wiki/Releases
Jan 23 16:57:29 <abelloni_> is about poky, not oe-core
Jan 23 16:57:51 <abelloni_> (that is the kind of remarks I get from $customers)
Jan 23 17:01:57 <rburton> abelloni_: in what sense?  poky is bitbake+oe-core, so what does it matter either way?
Jan 23 17:02:36 <joshuagl> then use sanity.conf as your source of info?
Jan 23 17:04:30 <abelloni_> yep
Jan 23 17:05:02 <abelloni_> rburton: well, I don't think it really mattered, I was asked the question and I didn't see anything good to reply
Jan 23 17:05:48 <abelloni_> I kind of find it cleaner to get oe-core + bitbake instead of getting poky and removing layers
Jan 23 17:05:59 <rburton> abelloni_: absolutely.
Jan 23 17:06:50 <abelloni_> but then people say "we will have to update the documentation and educate users"
Jan 23 17:08:20 <abelloni_> I think I will just say it doesn't matter
Jan 23 17:09:47 <abelloni_> Do you know whether it is possible to have a git over http mirror for a git+ssh SRC_URI ?
**** ENDING LOGGING AT Tue Jan 24 03:00:01 2017