All of lore.kernel.org
 help / color / mirror / Atom feed
From: <colin.helliwell@ln-systems.com>
To: <yocto@yoctoproject.org>
Subject: Slightly varying builds
Date: Wed, 1 Nov 2017 16:43:30 -0000	[thread overview]
Message-ID: <06ee01d35330$8d4102e0$a7c308a0$@ln-systems.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 459 bytes --]

I need to build two slightly varying versions of our Yocto build - one for
the production units and one for development.

They differ in only a few ways - the kernel and apps are the same. But one
has Dropbear, whilst the other doesn't; and the U-Boot configs & patches are
different.

 

I'm wondering where to do the separation - image, distro, conf.?

Any thoughts on the cleanest way to split and/or inherit them would be
appreciated.

 


[-- Attachment #2: Type: text/html, Size: 2340 bytes --]

             reply	other threads:[~2017-11-01 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 16:43 colin.helliwell [this message]
2017-11-01 17:04 ` Slightly varying builds Alexander Kanavin
2017-11-02  7:10   ` Colin Helliwell
2017-11-02 16:26     ` Colin Helliwell
2017-11-02 16:29       ` Alexander Kanavin
2017-11-02 16:50         ` Colin Helliwell
2017-11-02 16:59           ` Alexander Kanavin
2017-11-02 17:22             ` Colin Helliwell

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='06ee01d35330$8d4102e0$a7c308a0$@ln-systems.com' \
    --to=colin.helliwell@ln-systems.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.