From: Michael Wood <michael.g.wood@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Release and versions
Date: Thu, 19 Nov 2015 12:41:15 +0000 [thread overview]
Message-ID: <564DC36B.3030900@intel.com> (raw)
Hi,
We're currently manually maintaining a file[1] that maps metadata
release names e.g. 'fido' to the corresponding Bitbake version in
'toasterconf'. This is time consuming and confusing for people who are
running Bitbake/Toaster or Poky to work out which toasterconf is suited
for their setup.
Currently the only real need for these files is to know which Bitbake
versions are supported with which metadata versions, without someone
reading https://wiki.yoctoproject.org/wiki/Releases and editing a file
and submitting it. Would it make sense to make Bitbake versions match
those of it's metadata?
If departing from the current numbering scheme wouldn't be welcomed,
would there be room for a compromise where the Bitbake versions also
contain the release name e.g. 1.26_fido?
Thanks,
Michael
[1]
http://cgit.openembedded.org/openembedded-core/tree/meta/conf/toasterconf.json
next reply other threads:[~2015-11-19 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 12:41 Michael Wood [this message]
2015-11-19 12:58 ` Release and versions Richard Purdie
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=564DC36B.3030900@intel.com \
--to=michael.g.wood@intel.com \
--cc=bitbake-devel@lists.openembedded.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.