From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Bryan Evenson <bevenson@melinkcorp.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: is there a doc section on yocto distribution creation/versioning?
Date: Thu, 25 Jun 2015 12:43:47 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1506251241110.4028@localhost> (raw)
In-Reply-To: <BN3PR0501MB10900D0C13CEEC030AC648C5BBAE0@BN3PR0501MB1090.namprd05.prod.outlook.com>
On Thu, 25 Jun 2015, Bryan Evenson wrote:
> Robert,
>
> > -----Original Message-----
> > From: yocto-bounces@yoctoproject.org [mailto:yocto-
> > bounces@yoctoproject.org] On Behalf Of Robert P. J. Day
> > Sent: Thursday, June 25, 2015 6:29 AM
> > To: Yocto discussion list
> > Subject: [yocto] is there a doc section on yocto distribution
> > creation/versioning?
> >
> >
> > 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?
>
> If there is a writeup on this I have not seen it. I've developed a
> workflow on my own for our setup that works okay. Whether it'd be a
> recommended workflow or not is a different question.
... snip ...
backing up just a bit, i'm *assuming* this is a reasonable question
to ask, yes? if one wants to build for a custom product, one assumes
that product will have versioned releases and bug-fix releases, all
possibly based on some combination of different YP layers, each which
might have local enhancements, and all wrapped up with custom config
files. so defining a workflow to handle all this seems like a
reasonable thing to ask for. i'm surprised it hasn't already been
written up somewhere.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2015-06-25 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 10:28 is there a doc section on yocto distribution creation/versioning? Robert P. J. Day
2015-06-25 15:42 ` Bryan Evenson
2015-06-25 16:43 ` Robert P. J. Day [this message]
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.1506251241110.4028@localhost \
--to=rpjday@crashcourse.ca \
--cc=bevenson@melinkcorp.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.