From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6545369693963681792 X-Received: by 10.28.12.18 with SMTP id 18mr63845wmm.17.1523962643206; Tue, 17 Apr 2018 03:57:23 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.122.25 with SMTP id v25ls263480wmc.10.gmail; Tue, 17 Apr 2018 03:57:22 -0700 (PDT) X-Google-Smtp-Source: AIpwx49Gxumdp5Llfji6pp/RlMnt/bEn4kXknLwXPoCbCinupK+bccAIcwcfPF6tt27NBQpHVAYo X-Received: by 10.28.134.85 with SMTP id i82mr75052wmd.32.1523962642690; Tue, 17 Apr 2018 03:57:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523962642; cv=none; d=google.com; s=arc-20160816; b=e1PPYmCLsa53GTJzYW/+4b6BchC9zHfKxgS/kJCOCfhdbIm00LZmKpD6/ytnfxtgmi KeamfQUW4lp5TLiLxjUekjBV/jQT97jZgOAALT8Q/Te7xO4k+I4+C4BjfxE2j5L1qIqp lCDgGb4haZhFjP4sMyc0LmM3Z/GmJjUgEL4KcBZ295biUhWOlc6iEI9no3wD4ke8svtV 4D8AT5fHY6Dp8yABtClpABUSrE/gCRRGFFtEcSY0ECi/blmAk4QTuFaybsf2W0X8LK6o SwUgXhSk4vaAU51gzApbO/YcehH5N7U3bRLAxuSIAzwJEjnP+VeJfLoCxs9eOmNoDNgY e8bg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:references:to:from:subject :arc-authentication-results; bh=lMcGXeSlbjZhDG+tTaPIpDpEOhoj/d0DvQWw6V6exKY=; b=tL7ja5gf6kYRNNUGr1IPCk1K3oIYJY6RPzbnp0SJ1qiISQT9D4y5nfKi+ldj8MxYLY VaieagOEOwLy581NdYsdnbi9/6vJNuylntfczzCAyNFwBqEShnRTNWLbpv1Y8RBpF832 I33tCH+1YHHPNzikT3EmMtCxmkWMMckRaC+XWNqSOqP1SoUgXajpjn9CRvwPxLiCZYNa 1yZE+gLzpWQqo4ADgqN/kGbGfxpYupjQ+qyBr4ORS/mhuZAIQs45FDKnAmkOYwI41m8L d6ci6lft46BdAdqwsbCWXdR9o/S0eNDuVZLnXFE7Y1S3/cAfvbDCRVZny0TRPxttXv5o Dcgg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id w19si284290wra.4.2018.04.17.03.57.22 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Apr 2018 03:57:22 -0700 (PDT) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id w3HAvMCT022614 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 17 Apr 2018 12:57:22 +0200 Received: from [139.25.69.226] (linux-ses-ext02.ppmd.siemens.net [139.25.69.226]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id w3HAvLlq015350 for ; Tue, 17 Apr 2018 12:57:21 +0200 Subject: Re: [DISCUSSION] Directory structure of isar repo From: Claudius Heine To: isar-users References: <3a54efb1-4d93-c492-4d1a-b98d24dac570@siemens.com> Message-ID: Date: Tue, 17 Apr 2018 12:57:21 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <3a54efb1-4d93-c492-4d1a-b98d24dac570@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: k1VtCC+sWr9a Hi again, as promised, here are my reasons choosing this structure: On 2018-04-17 11:22, Claudius Heine wrote: > > . > ├── meta-isar meta-isar is in principle the old 'meta' directory. I did this because I think pushing 'meta-isar' as a general prefix to all meta layers related to isar makes it easier to distinguish them from OE meta layers. This makes it also easier to find other public isar metalayers. > │   ├── classes > │   │   ├── base.bbclass > │   │   ├── dpkg-base.bbclass > │   │   ├── dpkg.bbclass > │   │   ├── dpkg-raw.bbclass > │   │   ├── ext4-img.bbclass > │   │   ├── image.bbclass > │   │   ├── isar-bootstrap-helper.bbclass > │   │   ├── isar-events.bbclass > │   │   └── patch.bbclass > │   ├── conf > │   │   ├── isar-bitbake.conf > │   │   └── layer.conf > │   ├── lib > │   │   └── oe > │   │       └── path.py > │   ├── licenses > │   │   ├── COPYING.GPLv2 > │   │   └── COPYING.MIT > │   ├── recipes-core > │   │   ├── images > │   │   │   ├── isar-image-base.bb > │   │   │   └── isar-image-debug.bb I added the isar-image-base to the old 'meta' now 'meta-isar' directory, because it pretty much mostly used as the 'core-image-minimal' of OE, and that is part of its main layer. > │   │   └── isar-bootstrap > │   │       ├── files > │   │       │   └── isar-apt.conf > │   │       └── isar-bootstrap.bb > │   ├── recipes-devtools > │   │   ├── buildchroot > │   │   │   ├── buildchroot.bb > │   │   │   └── files > │   │   │       ├── build.sh > │   │   │       └── configscript.sh > │   │   └── isar-apt > │   │       ├── files > │   │       │   └── distributions.in > │   │       └── isar-apt.bb > │   └── recipes-kernel > │       ├── linux > │       │   ├── files > │       │   │   └── build-kernel.sh > │       │   ├── linux-custom.inc > │       │   └── linux-distro.bb > │       └── linux-module > │           ├── files > │           │   └── debian > │           │       ├── changelog > │           │       ├── compat > │           │       ├── control > │           │       └── rules > │           └── module.inc > ├── meta-isar-debian 'meta-isar-debian' contains all the files and configuration for the mainline debian distribution. Maybe it makes even sense to include this to 'meta-isar' since Debian is the mainline. Other meta-layers at a similar level could be 'meta-isar-ubuntu' or 'meta-isar-raspbian'. > │   ├── conf > │   │   ├── bblayers.conf.sample > │   │   ├── distro > │   │   │   ├── debian-jessie.conf > │   │   │   ├── debian-jessie.list > │   │   │   ├── debian-stretch.conf > │   │   │   ├── debian-stretch.list > │   │   │   ├── debian-wheezy.conf > │   │   │   └── debian-wheezy.list > │   │   ├── layer.conf > │   │   ├── local.conf.sample > │   │   ├── machine > │   │   │   ├── qemuamd64.conf > │   │   │   ├── qemuarm64.conf > │   │   │   ├── qemuarm.conf > │   │   │   └── qemui386.conf > │   │   └── multiconfig > │   │       ├── qemuamd64-jessie.conf > │   │       ├── qemuamd64-stretch.conf > │   │       ├── qemuarm64-stretch.conf > │   │       ├── qemuarm-jessie.conf > │   │       ├── qemuarm-stretch.conf > │   │       ├── qemuarm-wheezy.conf > │   │       ├── qemui386-jessie.conf > │   │       └── qemui386-stretch.conf > │   └── recipes-core > │       └── images > │           ├── files > │           │   └── debian-configscript.sh > │           └── isar-image-base.bbappend > ├── meta-isar-example All real example code I moved there as well as the raspbian configuration. I moved the raspbian configuration here for a couple of reasons: - Its a good example how to customize Isar to use a different repo and create a bsp. - While Isar supports raspbian, that support is currently not very well maintained. We only support RPi1 AFAIK. Its better if someone more interested in maintaining this port does it IMO. > │   ├── classes > │   │   └── rpi-sdimg.bbclass > │   ├── conf > │   │   ├── distro > │   │   │   ├── raspbian-jessie.conf > │   │   │   └── raspbian-jessie.list > │   │   ├── layer.conf > │   │   ├── machine > │   │   │   └── rpi.conf > │   │   └── multiconfig > │   │       └── rpi-jessie.conf > │   ├── recipes-app > │   │   ├── example-hello > │   │   │   ├── example-hello.bb > │   │   │   └── files > │   │   │       ├── 0001-Add-some-help.patch > │   │   │       └── yet-another-change.txt > │   │   ├── example-raw > │   │   │   ├── example-raw_0.2.bb > │   │   │   └── files > │   │   │       ├── postinst > │   │   │       └── README > │   │   └── libhello > │   │       └── libhello.bb > │   ├── recipes-core > │   │   └── images > │   │       ├── files > │   │       │   └── raspbian-configscript.sh > │   │       └── isar-image-base.bbappend > │   ├── recipes-kernel > │   │   ├── example-module > │   │   │   ├── example-module.bb > │   │   │   └── files > │   │   │       └── src > │   │   │           ├── example-module.c > │   │   │           └── Makefile > │   │   └── linux > │   │       ├── files > │   │       │   └── x86_64_defconfig > │   │       ├── linux-cip_4.4.bb > │   │       └── linux-mainline_4.14.18.bb > │   └── scripts > │       └── lib > │           └── wic > │               └── canned-wks > │                   └── sdimage-efi.wks > ... > Cheers, Claudius -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de