public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [DISCUSSION] Directory structure of isar repo
Date: Tue, 17 Apr 2018 12:57:16 +0200	[thread overview]
Message-ID: <f9a75cbd-c1fa-0784-64c9-dd5f37859108@siemens.com> (raw)

Hi,

since the last discussion about the directory structure went a bit stale 
I wanted to restart it here and present my suggestion.

Here is a mockup of a subset of the directory tree how I would try to 
improve it. I will leave some comments about my reasons in the next mail.

Cheers,
Claudius

.
├── meta-isar
│   ├── 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
│   │   └── 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
│   ├── 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
│   ├── 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
...


-- 
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

             reply	other threads:[~2018-04-17 10:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 10:57 Claudius Heine [this message]
2018-04-17 11:49 ` Jan Kiszka
2018-04-17 12:46   ` Claudius Heine
     [not found] <3a54efb1-4d93-c492-4d1a-b98d24dac570@siemens.com>
2018-04-17 10:57 ` Claudius Heine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f9a75cbd-c1fa-0784-64c9-dd5f37859108@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox