From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: is there a doc section on yocto distribution creation/versioning?
Date: Thu, 25 Jun 2015 06:28:36 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1506250625460.5572@localhost> (raw)
is there a recommended workflow for tagging/versioning one's own
builds from yocto? that is, given the collection of layers that might
go into one's local builds, in order to properly version your builds
for release, one would have to keep track of not only the checkouts of
the various layers, but any local fixes added to them, combined with
all of the local conf settings used for that build, and so on.
is there a writeup on this?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2015-06-25 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 10:28 Robert P. J. Day [this message]
2015-06-25 15:42 ` is there a doc section on yocto distribution creation/versioning? Bryan Evenson
2015-06-25 16:43 ` Robert P. J. Day
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=alpine.LFD.2.11.1506250625460.5572@localhost \
--to=rpjday@crashcourse.ca \
--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.