[bitbake-devel] Question on toaster bringup

[Reyna, David]

Hi Olaf,

Thank you for using Toaster! There is a Toaster team and we have a meeting each week, for which I am the lead and the Toaster maintainer. I will forward you the link (it is in about 10 minutes :-)

1) See 11957 for a resolution for your question. The fixtures are strictly additive, so 11957 provides the way to disable the default fixtures.

2) Yes, create and enhancement request and we can address that. It is too late for enhancements for YP-2.4 but we can look at that for 2.5.

3) Ideally you would provide your own Layer Index server so that you can get the full power of the interface. We can certainly look at alternatives for your reduced use case.

- David Reyna

-----Original Message-----
From: bitbake-devel-bounces at lists.openembedded.org [mailto:bitbake-devel-bounces at lists.openembedded.org] On Behalf Of Olaf Mandel
Sent: Wednesday, August 30, 2017 5:39 AM
To: bitbake-devel at lists.openembedded.org
Subject: [bitbake-devel] Question on toaster bringup

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello,

I want to initialize toaster from fixtures alone, if possible. It should
only provide a "local" release (no network dependency at all). Here I
ran into two to three problems:

* the oe-core.xml fixture adds three releases. Is it possible to
remove/delete objects in the custom.xml fixture that I do not want?
Currently I am working around that by just configuring out the line
call_command("loaddata", "oe-core") in checksettings.py.

* the custom.xml fixture needs to reside in the
bitbake/lib/toaster/orm/fixtures directory to be found. How can I search
at other places? Setting an environment variable FIXTURE_DIRS didn't
seem to help.

* minor point: would it make sense to detect if
call_command("lsupdates") is needed? One does not need that for a purely
local release and I have it commented out.

Thank you for your time,
Olaf
- -- 
Olaf Mandel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJZprHhAAoJEFS9nbRiUh3/YeEIAIWvZIb0gECYO+mTrcZu+7w7
Zmtg2ZcYM2BWwthzJl4aA48vVjwYOpY74oQnByorEJh6yjSob/GqAFgPKbNGVF+a
zH1BCkzao7oAdYtY5naYfYyaD5iDvStl/pfxCoxujh7wC9k7o11gBXO2HIp4U/Ww
8kiNlDpjI2dOciuanYB9hluOtwJ+pBJsuFhktTRKn3f7hSkPq1Q/C+L8dJEBc9sl
JyQ5yNdEhXhrvCPT1wyJtxnHiAXIK/nQrXb0uEFzLv1ENxgCiGVxY6GsHm7KSXf/
I53I+m5kWiBozgo5bXPfj6W0se/v7EsU30kOCilUCAf6bl65LS2EyqVndTJCHZ4=
=GW/i
-----END PGP SIGNATURE-----
-- 
_______________________________________________
bitbake-devel mailing list
bitbake-devel at lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/bitbake-devel