Hi Sujith,
Thanks for the ping. My thoughts on this...
I had a look at those patches and unfortunately I think it's just too
much of a work-around to push this into the toaster at the moment.
That's not to say that this isn't something that we want to fix. There
are at least two larger problems that need to be solved for this:
1) i) Allow non-git layers in the project configuration
ii) Change the UI assumptions that layers are in GIT
iii) Fixing up the localhostbecontroller
2) Fix the setting up of Toaster to allow pre-defined configurations
Currently we scan a slightly unwieldy toasterconf.json to load in a lot
of the initial data. The more standard way of doing this is to use the
fixtures feature of Django
https://docs.djangoproject.com/en/1.8/howto/initial-data/
Having used the fixtures for unittests I'm wondering if in our toaster
setup routine we load some fixtures and provide a directory which is
scanned like lib/toaster/fixtures.d/ where people can remove or add to
with their own fixtures whether that combined with (1) might meet your
needs.
Thanks,
Michael
On 27/04/16 17:06, sujith h wrote:
A gentle ping. There is a request from Mentor to review this patch.
The release would be pre 2.2 release ( around august 2016) for us at
Mentor. And hence if we can get through this change, that would be
helpful. Or if we can get
https://bugzilla.yoctoproject.org/show_bug.cgi?id=8456 before 2.2 that
would be helpful too. Because both address same cause.
On Fri, Mar 18, 2016 at 6:29 PM, sujith h <[email protected]
<mailto:[email protected]>> wrote:
Hi,
Mentor Graphics is planning for yocto 2.2 release. I believe we
have plenty of time. But still organization wants me to get
through with these patches to upstream. So I have pushed couple of
commits in
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sujith/toaster-no-git-layers.
This patch should work as below:
1) Except poky all the other layers or dirs should be non-git
2) A script is added which will auto generate toasterconf.json
file based on the information from the bblayers.conf. So the user
should have the required layers already populated in the
bblayers.conf. To run the script user will have to provide the
conf directory path as option. ( like
--confdir=/home/sujith/gitroot/poky/build/conf ). This conf
directory will be the location where local.conf and bblayers.conf
will be residing.
3) Export toasterconf.json file which will be created in the build
directory. For example:
export
TOASTER_CONF=/home/sujith/gitroot/poky/build/toasterconf.json
4) Run toaster.
5) User should be able to see the layers in the UI. Which should
be ready for the build.
Thanks,
Sujith H
--
സുജിത് ഹരിദാസന്
Bangalore
<Project>Contributor to KDE project
<Project>Contributor to Yocto project
http://fci.wikia.com/wiki/Anti-DRM-Campaign
<Blog> http://sujithh.info
--
സുജിത് ഹരിദാസന്
Bangalore
<Project>Contributor to KDE project
<Project>Contributor to Yocto project
http://fci.wikia.com/wiki/Anti-DRM-Campaign
<Blog> http://sujithh.info
C-x C-c
--
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster
