**** BEGIN LOGGING AT Wed Jul 30 03:00:01 2014 Jul 30 07:30:13 pidge, hi we send some emails back and forth about the yocto autobuilder, how is the documentation coming ? Jul 30 07:33:21 i would realy like to read it Jul 30 09:37:26 pidge: hi, we have exchanged e-mails about the yocto-autobuilder how is the documentation comming? Jul 30 09:58:49 morning all Jul 30 12:27:00 pidge: hi, we have exchanged e-mails about the yocto-autobuilder how is the documentation comming? Jul 30 13:24:23 i try to get an understanding of bitbake. So i have a basic setup of bitbake and look into the base.bbclass. Why is the task do_fetch defined as a function "base_do_fetch". Can i reference it from other classes? Jul 30 13:27:41 fragfutter, you can inherit classes, so something else could do "inherit base". i think the naming base_do_fetch() is just a way to prevent namespace collisions, in case the class that inherits base also wants a do_fetch, that possibly overrides the base do_fetch. Not sure if this is the reason though, just guessing :) Jul 30 13:28:48 mago_: if i inherit i can simply override it. No nameclash. The question is how i get to call the original from the parent. Jul 30 13:29:59 bluelightning can answer these questions for sure ;-) Jul 30 13:30:10 he is like the bitbake dad in this channel Jul 30 13:30:20 heh Jul 30 13:31:21 fragfutter: I'd suggest reading the bitbake manual section on this and then by all means if you have further questions I'll be happy to answer them Jul 30 13:31:23 fragfutter: http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#flexible-inheritance-for-class-functions Jul 30 13:31:45 base.bbclass is automatically inherited globally, FYI Jul 30 13:31:54 bluelightning: hi bitbake dad :) Jul 30 13:32:04 RP: does that make you bitbake grandad? ;) Jul 30 13:32:15 bluelightning: I dread to think... Jul 30 13:35:15 bluelightning: got it. thanks Jul 30 13:53:30 wfailla: It's slow but steady. I have some pulled already but the big docs are in the works Jul 30 13:54:19 bluelightning: the rm_work option removes the work dir of a package, the RM_WORK_EXCLUDE excludes some packages of this option, is there a way to remove old versions and only keep the workdir of the newes version of a package ? Jul 30 13:55:20 wfailla: there is an rm_old_work class that does that in meta-micro (IIRC); someone was suggesting bringing it into the core the other day though Jul 30 13:56:15 pidge: Great, can you email me a copy? Jul 30 13:57:06 wfailla: let me sync with LCryin Jul 30 13:58:32 bluelightning: Thanks! Jul 30 14:02:17 pidge: Who is LCryin ? Jul 30 14:02:42 I have tried to google it but without luck, I seem to use the wrong search words. I have a recipe and I want it to use the files I have locally in a directory instead of getting it from a server via git. What do I need to do? Jul 30 14:02:46 wfailla: Intern working on docs. Jul 30 14:04:07 I did this, but am getting just errors Jul 30 14:04:10 SRC_URI = "file:///home/jeena/Projects/qtivi/" Jul 30 14:04:10 SRCREV = "${AUTOREV}" Jul 30 14:04:44 ls: cannot access .../1.0+gitAUTOINC-r0/git//*.pro: No such file or directory and so on Jul 30 14:06:04 use git:// instead of file and add ;protocol=file in the end Jul 30 14:06:14 not sure if protocol is needed Jul 30 14:06:31 RP: thanks for looking into qemu-native issue and the patch Jul 30 14:06:56 that three dots meant to be an explicit abbrev. vs. a typo of ../ instead? Jul 30 14:07:00 RP: I've sent more detail in reply, small nitpick in your patch you're mixing spaces and tabs for indentation Jul 30 14:08:12 radhus, does it then use the changed files I have on my harddrive or does it check out the head on master (because it is a local copy of the repo)? Jul 30 14:09:40 sorry, if you use git:// I think it will clone your repository and not used the changed files. sorry if I've misinformed you Jul 30 14:09:49 and one funny thing is, the first time running it seems to work, the second time it throws this error: .../1.0+gitAUTOINC-r0/temp/run.do_install.27643: Install: not found Jul 30 14:10:44 it is weird that I can't find any howto page about it, where would I look for information like that? Jul 30 14:11:38 (after a cleansstate it works one time again) Jul 30 15:03:15 pidge: Any luck? Jul 30 15:04:40 wfailla: sorry, I'm not in yet ;). Just woke up. Jul 30 15:04:54 pidge: Sorry if I am a pain but I am really eager to see the documentation. ;) Jul 30 15:05:26 pidge: Oh what timezone are you in ? Jul 30 19:21:24 anyone done the adduser/deluser type stuff from debian in yocto before I go do it myself? I want to get away from everything busybox as much as possible. Jul 30 19:22:07 FWIW, rhel/centos type stuff just symlinks adduser to useradd etc etc. Jul 30 19:22:09 ? Jul 30 19:22:17 just enable the shadow utilities on the target.. Jul 30 19:22:36 the debian adduser/deluser isn't needed.. the version from shadow (useradd) is all that sneeded for descrete control Jul 30 19:22:54 fray_, in debian/ubu, they (adduser/deluser) are more user friendly perl script wrappers around useradd/userdel. Jul 30 19:22:54 debian utilities are just perl wrappers to the real ones.. and don't always work right with all of the shadow options enabled.. Jul 30 19:23:13 Sure they aren't needed, but I want them, since they reduce the suck factor of using the machine. **** ENDING LOGGING AT Thu Jul 31 03:00:00 2014