IRC log for #oe on 20191003

00:01.55*** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning)
00:05.51*** join/#oe tgamblin (~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com)
00:17.35*** join/#oe infobot (ibot@c-174-52-60-165.hsd1.ut.comcast.net)
00:17.35*** topic/#oe is OpenEmbedded Developer Lounge | Web: http://openembedded.org | Repositories: http://git.openembedded.org/ | Primary Repo Mirrors: https://github.com/openembedded | This is not a distro or machine support channel
01:17.59*** join/#oe nslu2-log (~nslu2-log@23.141.224.193)
01:39.30*** join/#oe Crofton (~Crofton@50.224.179.20)
01:46.23*** join/#oe nslu2-log (~nslu2-log@23.141.224.193)
02:25.28*** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning)
03:07.10*** join/#oe vmeson (~rmacleod@24-52-239-53.cable.teksavvy.com)
04:25.23*** join/#oe armpit (~armpit@2601:202:4180:a5c0:c4b4:7209:8fc9:6ab9)
04:32.09*** join/#oe AndersD (~AndersD@h83-209-191-235.cust.a3fiber.se)
04:34.26*** join/#oe AndersD_ (~AndersD@h-98-128-162-82.NA.cust.bahnhof.se)
05:12.06*** join/#oe leon-anavi (~Leon@78.130.245.102)
05:47.19*** join/#oe kroon (~kroon@213.185.29.22)
06:05.31*** join/#oe ao2 (~ao2@host7-208-static.12-87-b.business.telecomitalia.it)
06:16.52*** join/#oe Bunio_FH (~bunio@clj-165.netdrive.pl)
06:38.21*** join/#oe comptroller (~comptroll@47-213-222-253.paolcmtc01.res.dyn.suddenlink.net)
06:50.28*** join/#oe Bunio_FH (~bunio@clj-165.netdrive.pl)
07:20.03*** join/#oe cpriouzeau (~cpriouzea@164.129.115.76)
07:23.40*** join/#oe tprrt (~tprrt@upc31-1-78-208-110-13.fbx.proxad.net)
07:36.55*** join/#oe Bunio_FH (~bunio@81-18-201-214.static.chello.pl)
08:09.10*** join/#oe yann (~yann@85.118.38.73)
09:00.12*** join/#oe rburton (~rburton@35.106.2.81.in-addr.arpa)
09:17.47*** join/#oe florian (~florian_k@Maemo/community/contributor/florian)
11:15.51*** join/#oe bluelightning_ (~paul@pdpc/supporter/professional/bluelightning)
11:17.35*** join/#oe florian (~florian_k@Maemo/community/contributor/florian)
11:27.44*** join/#oe ao2 (~ao2@host7-208-static.12-87-b.business.telecomitalia.it)
11:38.05*** join/#oe berton (~berton@181.220.83.67)
11:41.38*** join/#oe tgamblin (~tgamblin@128.224.252.2)
11:53.21*** join/#oe berton (~berton@181.220.83.67)
12:06.47*** join/#oe dv_ (~dv@62.178.50.190)
12:54.05*** join/#oe radsquirrel (~bradleyb@mail.fuzziesquirrel.com)
13:43.08*** join/#oe comptroller (~comptroll@47-213-222-253.paolcmtc01.res.dyn.suddenlink.net)
13:49.59*** join/#oe nabokov (~armand@67.218.223.154)
14:15.37*** join/#oe florian (~florian_k@Maemo/community/contributor/florian)
14:32.45*** join/#oe nabokov (~armand@67.218.223.154)
15:47.45*** join/#oe Crofton (~Crofton@167.220.58.17)
15:56.09Croftonhttps://blog.3mdeb.com/2019/2019-02-07-kas/
15:56.54*** join/#oe kroon (~kroon@37-247-29-68.customers.ownit.se)
15:58.56CroftonThese guys have great points
16:02.38kergothhmm, it's interesting, but seems fairly invasive to the workflow, and has its own limitations. might have to poke at it, though
16:08.32JPEWkergoth, Crofton: It's interesting how different groups try to solve the same problem, we made: https://github.com/garmin/pyrex
16:11.11kergothJPEW: i like the transparent docker approaches. fuck development INSIDE the thing, just run bitbake there and don't muck with my setup
16:11.23kergothi hack it with sudo docker run --rm -it --privileged -u "$(id -u):$(id -g)" -v "$resolv:/etc/resolv.conf" -v "$PWD:$PWD" -v "$PWD/..:$PWD/.." -v ~/.ssh:/home/build/.ssh -v "$XDG_CONFIG_HOME/git:/home/build/.config/git" industrial-vm:latest /bin/bash -c "cd \"$PWD\" && env \"PATH=$PATH\" \"BUILDDIR=$BUILDDIR\" \"INDUSTRIAL_SOURCES=$INDUSTRIAL_SOURCES\" \"BB_ENV_EXTRAWHITE=$BB_ENV_EXTRAWHITE\" bitbake \"\$@\"" or equivalent, with manual tweaks. not pretty,
16:11.23kergothbut..
16:11.24JPEWkergoth: Exactly
16:12.06CroftonWe need to collect all this info and have a bext practices list page
16:12.24Croftonand say migrate away from repo :)
16:12.36kergothi'm not sure best practices *exist* here, everyone keeps rolling new tools for it :)
16:12.55kergothoe should have had their own back in the beginning before everyone got used to the capabiliteis of their own tooling :)
16:13.28Croftonkergoth, the problem is no one has the time to figure that out.
16:13.45CroftonSo now we need to review what eople do and work ouy the good and bad of each
16:13.56kergothit's nice that there are tools to simlpify the docker based setup now, both kas and pyrex are better than handcrafted shit
16:13.58CroftonAs I said earlier, we have a very diverse user base
16:14.08kergothyeah, trying to satisfy the workflow needs of everyone is a tough one
16:14.12kergothwidely varied needs
16:14.16Croftondocker wasn;t invented when OE was invented
16:14.29JPEWEven just somewhere that *listed* all the options would be helpful
16:14.35Croftonright
16:14.39kergothtrue, but then tools like kas take on other aspects, not just docker. but yeah, a Docker page in the oe wiki would probably be a good idea
16:14.49Croftonthere is a wind river created one
16:15.02Croftonhmm, sounds like a job for the OE TSC :)
16:15.10JPEWI think detailing the pros/cons of each would be helpful, too
16:15.15kergothi've tried using crops, but i did not take to that stuff *at all*, i ended up just using cbrake/oe-build with a wrapper function like the above
16:15.15JPEWCrofton: Noted
16:15.47Croftonand by that I mean show leadership, not consume huge amounts of your time
16:15.52JPEWIMHO, crops is the "I just want to build it to try it out tool". It's not a dev environment
16:15.59kergothnods
16:16.15CroftonOK I need to fix something for someone who pays me
16:16.28CroftonI could starve doing useful stuff like this :(
16:16.31kergothseems like there's 3 key aspects to a more transparent approach: passing env vars in, adding numerous bind volumes, and dealing with uid/gid mapping.
16:16.52kergothheh, i should get back to banging my head on this intractable task myself
16:17.22Croftonheh
16:17.35JPEWkergton: You should look at how pyrex handles the UID/GID mapping sometime. It's.... interesting :)
16:19.27kergoththe one i'm using at the moment just checks if the current uid/gid doesn't match up witht he build user inside and changes it if needed. cheap but gets the job done
16:19.37kergothyeah i'll take a look for sure
16:23.35CroftonThese would be called Layer Management Systems?
16:41.49JPEWCrofton: kas looks like it might do some layer management, but the others (pyrex, CROPS) don't
16:49.01CroftonWhat should i call a wiki page to collect these links?
16:58.49kergoth<3 git-revise so much
17:04.35*** join/#oe Bunio_FH (~bunio@clj-165.netdrive.pl)
17:05.09*** join/#oe ao2 (~ao2@host7-208-static.12-87-b.business.telecomitalia.it)
17:10.38*** join/#oe tgamblin (~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com)
17:20.53CroftonJPEW, how do you describe pyrex?
17:22.52JPEWCrofton: Seamless Docker container setup for developing with OpenEmbedded/Yocto Project
17:23.07JPEWI *think* most docker users will understand what that means
17:23.45Croftonhmm, I am looking for a name for a wiki page :)
17:24.35JPEWDocker container build tools?
17:24.53JPEWBuilding in a Docker container?
17:28.10Croftonseems like there are two things, handling layes and docker configs
17:28.19Crofton:Build management tooling
17:28.41Croftonso many visors
17:32.13*** join/#oe Bunio_FH (~bunio@clj-165.netdrive.pl)
17:37.25JPEWCrofton: I really need a sunvisor.... I get why the presenters are being blinded, but the light on the audience are annoying
17:40.26Croftonah I see, I am just far enough back to avoid it
17:50.55*** join/#oe Bunio_FH (~bunio@clj-165.netdrive.pl)
17:54.11*** join/#oe Bunio_FH (~bunio@clj-165.netdrive.pl)
18:33.01*** join/#oe stefan_schmidt (~stefan_sc@p200300E9D72FE0CABFAA25D3F9EBE8A1.dip0.t-ipconnect.de)
18:47.43*** join/#oe comptroller (~comptroll@47-213-222-253.paolcmtc01.res.dyn.suddenlink.net)
19:04.23*** join/#oe BlastuR (~magnus@unaffiliated/blastur)
19:04.56*** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning)
19:07.32*** join/#oe armpit (~armpit@45.19.219.178)
19:21.38CroftonPlease add to this page, then we need to classify better and start listing strengths and weknesses
19:21.40Croftonhttps://www.openembedded.org/wiki/Build_Management_Tooling
19:29.24*** join/#oe tanuk (~quassel@185.87.111.182)
19:33.38*** join/#oe Bunio_FH (~bunio@clj-165.netdrive.pl)
20:13.50*** join/#oe ao2 (~ao2@host7-208-static.12-87-b.business.telecomitalia.it)
21:22.18*** join/#oe Bunio_FH (~bunio@clj-165.netdrive.pl)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.