On 24/03/15 11:35, Barros Pena, Belen wrote:
On 24/03/2015 11:29, "Michael Wood" <[email protected]> wrote:
Looks good to me.
Thanks
Related comment (but not impacting on this review) - I've always found
it weird that releases == git branches in toaster, that seems like an
implementation detail to me, as in other projects a release could be a
git tag or a tarball or a commit or any of the 100s of ways of
distributing code.
I didn't think this was the case. I was under the impression that a
release was a combination of a BitBake version and a OE metadata version.
What that version is set to (a branch, a git tag or a commit) should be
irrelevant (we should be supporting all 3, but not tarballs I think).
What makes you think that a release must be a git branch?
The configuration for the release field names are "branch" and "up_branch"
(http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/toasterconf.json?#n62)
Cheers
Belén
On 22/03/15 20:17, belen barros pena wrote:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=bbarrosp/ui
-fixes
a8a5552ad7d3ba869f165ef4a392990263224428
bitbake: toasterui: hide right column if empty
cf44f4dfe7a6dec273d77143dbe19eeab1ae23d5
bitbake: toasterui: Improve messaging for empty layer details
09246f125cea1f8ff81081492824e14a3d38b02c
bitbake: toasterui: hide release when only one exists
a2ffbc6f186f7d7fb022c8bfcd5b01a1a3442bb6
bitbake: toaster: update OpenEmbedded Toaster configuration
015fac8c6ef58218c8ad75d375907f13ac021548
bitbake: toaster: update Yocto Project Toaster configuration
Thanks,
Belén
--
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster
--
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster