**** BEGIN LOGGING AT Sat Jul 27 02:59:58 2013 Jul 27 06:37:07 would it be acceptable to at least put the required packages on arch into the documentation even if it is an unsupported platform? Jul 27 07:06:40 ndec: which mailing list to send a patch to, about removing the deprecated x-load for beagleboard? Jul 27 07:06:55 yocto@ or poky@? I guess the former? Jul 27 07:07:16 is there a guideline somewhere about the separation? Jul 27 08:38:11 what is perl used for in Yocto? Jul 27 09:45:15 kergoth: did you get the chance to reproduce the /usr installation issue? Jul 27 16:33:24 can I instruct bitbake to build a certain layer? I mean the packages inside ... say, my meta-qt5 layer. Jul 27 16:50:21 i think the way to do that might be a package group Jul 27 16:51:22 yeah, but how to do that? Jul 27 16:56:01 actually, you could probably just make a meta recipe Jul 27 16:56:14 meta/recipes-multimedia/gstreamer/gst-meta-base_0.10.bb <= like this Jul 27 16:57:44 haven't tried it yet... Jul 27 17:40:03 nerdboy: bluelightning: http://paste.kde.org/~lpapp/pd928c826/ Jul 27 17:40:13 what is this python issue? Jul 27 17:49:42 just what it says, but i have no idea why it's trying to open fstab Jul 27 17:50:56 wth is smart/media.py? Jul 27 17:51:33 nerdboy: I do not know. Jul 27 17:52:48 is fstab not publicly readable on arch? Jul 27 17:54:23 all i see in the traceback is open() so i assume it's a read-only open... Jul 27 17:54:48 what are the perms on fstab? Jul 27 17:58:50 ls -l /etc/fstab Jul 27 17:58:50 -rw------- 1 root root 386 Jan 5 2013 /etc/fstab Jul 27 17:59:00 that would be it... Jul 27 17:59:43 what is your permission on that file, then? Jul 27 17:59:58 world readable Jul 27 18:00:02 -rw-r--r-- 1 root root 4476 Oct 7 2012 /etc/fstab Jul 27 18:00:14 544, ok. Jul 27 18:00:42 on gentoo/debian/ubuntu Jul 27 18:00:47 all the sane Jul 27 18:00:54 k Jul 27 18:01:57 not sure why it cares about discovering media on the build host Jul 27 18:03:08 k, it is built now, thanks. Jul 27 18:03:26 seems potentially risky depending on what it's trying to do... Jul 27 18:04:08 yeah. Jul 27 18:05:02 i'm pretty new to yocto, but do you have something in your config that enables automatically deploying to an sdcard or something? Jul 27 18:06:00 if so, that would be a feature i didn't know about... Jul 27 18:12:17 it is vanilla poky Jul 27 18:12:19 latest master. Jul 27 18:19:29 JaMa|Off: oh, it is you maintaining the meta-qt5 layer. Jul 27 18:22:06 i'm building off poky master also Jul 27 18:22:43 depending on what's in your configs, image recipes, etc, it could be very different Jul 27 18:30:13 nothing special really. Jul 27 18:30:23 except the external toolchain, it is pretty much the default. Jul 27 18:43:22 * nerdboy is enjoying his new arm chromebook hack Jul 27 18:46:10 nerdboy: :) Jul 27 18:46:17 enjoying things is fun. Jul 27 18:49:16 nerdboy: shouldn't the layer document how to build the layer? Jul 27 18:49:22 or is it just generic for any layer? Jul 27 18:53:39 the layer doc i inherited in my fork is a readme that tells you what other layers it depends on Jul 27 18:54:13 that plus a few image features is pretty much it Jul 27 18:54:43 yeah, but the interesting question is how to build the recipes in the layer. Jul 27 18:54:49 i used some "getting started" web page for that part.. Jul 27 18:55:15 normally you just add the package names you want to an image recipe Jul 27 18:55:44 you can inherit other images add packagegroups, etc Jul 27 18:56:25 first thing i did was build existing (albeit bare-bones) pi images Jul 27 18:56:28 ok, so people usually create their own image files. Jul 27 18:56:49 or "borrow" from other layers... Jul 27 18:57:12 well, I mean they have their own image files. Jul 27 18:57:15 whatever it does internally. Jul 27 18:57:26 so they do not usually use exiting ones off-hand. Jul 27 18:57:29 i also made the sato image before i decided to make my own Jul 27 18:58:49 beyond the basic oe-core images, it really depends Jul 27 18:59:09 there are gnome, xfce, qt and efl images in various layers Jul 27 18:59:57 i didn't like the dependencies or bloatiness of the above, so i kinda needed to make my own minimal X image Jul 27 19:01:03 thus, rpi-xorg-image.bb was born Jul 27 19:01:45 which you could easily build for other machines if you remove the one or two-rpi specific packages Jul 27 19:03:43 normally you would refer to virtual/kernel so even that should be fine in another machine config Jul 27 19:03:49 I guess there is a description somewhere how to build your own custom image. Jul 27 19:03:54 I have always used this core-image-minimal. Jul 27 19:04:27 well, we have our own custom kernel. Jul 27 19:04:36 alongside the custom u-boot, busybox, et cetera. Jul 27 19:04:56 minimal is pretty minimal... Jul 27 19:05:13 i had to stop inheriting that to get what i wanted Jul 27 19:05:44 try core-image instead if you want a more "normal" environment Jul 27 19:05:47 I personally dislike the meta-foo naming. Jul 27 19:05:54 why cannot it have its own dedicated meta folder? Jul 27 19:06:07 no no, I wanna have a minimal, really. Jul 27 19:06:18 we have a very small nor flash. Jul 27 19:06:24 i'm assuming that was discussed ad nauseum Jul 27 19:06:47 * nerdboy wasn't involved in that discussion Jul 27 19:07:09 not much to discuss about it. Jul 27 19:07:12 small nor flash is small. Jul 27 19:07:21 not the flash... Jul 27 19:07:22 you cannot physically put a lot of stuff on it. Jul 27 19:07:56 for that you would probably want to stick with core-image-minimal Jul 27 19:08:36 *the naming scheme discussion... Jul 27 19:09:23 how much flash do you have? Jul 27 19:09:28 32 MB Jul 27 19:09:33 ow Jul 27 19:13:42 we don't have the NOR flash option on our TI board, but i think we have 256 MB of NAND Jul 27 19:14:19 ,ultiple redundant kernels and rescue rootfs's Jul 27 19:15:01 since we're now running off an ssd the normal kernel has to live in nand too Jul 27 19:21:29 nerdboy: well, it would be nice to be able to build the qt5 packages without an image. Jul 27 19:21:35 "bitbake qt5" or so. Jul 27 19:21:40 once the layer is cloned properly. Jul 27 19:25:33 that would take a meta recipe Jul 27 19:25:48 nerdboy: that is bad Jul 27 19:25:53 why two separate layers? Jul 27 19:26:00 when the qt5 layer could define it on its own. Jul 27 19:26:00 you need one or the other as a bitbake target Jul 27 19:26:11 you have to bitbake something Jul 27 19:26:14 it should be only a meta recipe Jul 27 19:26:21 not a separate layer for one particular recipe. Jul 27 19:26:32 you bitbake packages, not layeres. Jul 27 19:26:34 layers* Jul 27 19:26:43 you can add recipes wherever you like Jul 27 19:27:14 i had to add several layers to my config because the packages i wanted are spread all over the place Jul 27 19:27:47 yeah, but a qt5 layer is dedicated for that, don't you think? :) Jul 27 19:27:58 regardless, to get what you want you need an image or meta recipe to bitbake Jul 27 19:28:07 also a recipe in a layer can depend on a recipe in another layer as far as I understand. Jul 27 19:28:31 yeah, but i would hope that's not *too* common Jul 27 19:29:05 well, look at meta-qt5 Jul 27 19:29:12 they do not have any other chance than depending in oe-core Jul 27 19:29:16 and recipes inside meta/ Jul 27 19:30:01 it makes sens for meta, but not so much for random layers... Jul 27 19:31:30 well, it makes sense for meta-xilinx, too. Jul 27 19:31:42 which depends on meta-sourcery; it is just one of those. Jul 27 19:32:46 my expectations about loose coupling are probably off Jul 27 19:33:45 better if there's not too much coupling between ad-hoc layers, but maybe that's normal Jul 27 19:34:08 I think it is normal to have many layers. Jul 27 19:34:16 and build softwares on top of each other. Jul 27 19:38:23 yes, but in some cases it's more of a sideways pull rather than a logical layering Jul 27 19:39:37 at least for my "lite" xorg image i need about 7 layers... Jul 27 19:40:26 and that's without building any kind of xfce/gnome/qt/efl desktop Jul 27 19:40:52 funky. Jul 27 19:42:04 it parses recipes much better than old versions of bitbake/oe-classic so it's not painful or anything Jul 27 19:42:19 but it does seem funky... Jul 27 19:42:37 parses and caches Jul 27 19:47:17 too bad Yocto does not support pacman. Jul 27 19:56:58 i'm using opkg Jul 27 19:57:14 not sure the other package support is fully fleshed out Jul 27 19:58:25 i tried the deb package support but it didn't seem to be working correctly Jul 27 19:58:55 really? Jul 27 20:00:31 that was when i first set it up, so it may have been my config Jul 27 20:01:01 i might try it again after i pull all the master branches Jul 27 20:02:04 https://bugzilla.yoctoproject.org/show_bug.cgi?id=4929 Jul 27 20:02:05 oops, 9 layers now... Jul 27 20:02:05 Bug 4929: normal, Undecided, ---, dvhart, NEW , Add support for pacman as package_pacman/xy.bbclass Jul 27 20:43:25 nerdboy: what are you working on Jul 27 20:52:00 a no-systemd bbappend for gpsd atm... Jul 27 20:52:37 otherwise qa yells at you about unpackaged files... Jul 27 21:00:33 lpapp: I saw your earlier question about maintaining a list of Arch packages for the Yocto Porject, since you seem to have a keen interest in it working, would you be willing to maintain such a wiki page? Since it's not a supported distro, the team does not really have the installed base, this was one reason I asked you about the package list once before. Your help with this would be greatly apperciated. Jul 27 21:02:42 nope, I dislike wikis. Jul 27 21:02:54 package list is useless Jul 27 21:02:58 it is bloated Jul 27 21:03:03 people need more self-contained stuff. Jul 27 21:03:38 I believe you did not go far with the package list. Jul 27 21:11:20 sgw_: besides, I am not that motivated as arch has been voted down by 1-2 people on the mailing list. Jul 27 21:11:32 so I only put as much effort into this as really needed. Jul 27 22:20:39 lpapp: sorry, I had to step away, well your help is the area would be valuable to others, and you reopen the bugs requesting documentation, some of that documentation has to come from users of Arch, not all, but some. Jul 27 22:28:51 unfortunately, I am not in a position to help if arch is rejected. Jul 27 22:36:52 really oe needs a way to declare host dependencies Jul 27 22:37:33 and emit them in a distro-independent way, like pkgconfig(zlib) instead of hardcoding zlib-devel Jul 27 22:37:49 like we did for jhbuild Jul 27 23:01:30 nerdboy: I meant what project at the company Jul 27 23:01:36 what the embedded end product is. Jul 28 00:26:56 lpapp: oh, it's an endoscopic surgical camera Jul 28 00:29:36 google "synergy hd3" and you'll see it... **** ENDING LOGGING AT Sun Jul 28 02:59:58 2013