Bug 9760

Summary:	Make it easier to set up your own derivative layer index
Product:	[Yocto Project Subprojects] Layer Index	Reporter:	Paul Eggleton <bluelightning>
Component:	Layer Index	Assignee:	Unassigned <unassigned>
Status:	IN PROGRESS IMPLEMENTATION ---	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	akuster, brian.avery, konrad.scherer, liezhi.yang, piotr, randy.macleod, tim.orling
Version:	5.99
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Paul Eggleton 2016-06-13 04:34:47 UTC

If you want to set up your own "curated" layer index, currently you have to  enter the details for all of the layers manually. It would be useful if you could set up an index and "connect" it to the OE layer index, specifying which layers you want, and then have the info on just those layers synced across. You should also be free to add layers your layer index instance as normal.

Comment 1 Armin Kuster 2019-12-23 16:34:46 UTC

is this still an issue?

Comment 2 Tim Orling 2023-09-30 23:52:28 UTC

This is mostly handled by the dockersetup.py script?

Comment 3 Tim Orling 2025-10-02 15:07:07 UTC

We have some new work going on around docker-compose workflow thanks to Piotr.

Comment 4 Tim Orling 2025-10-02 15:16:36 UTC

Perhaps we could have a yaml or other similar input of a "curated" list of layers to ingress into the initial database (perhaps an "allow" and "exclude" concept). This would save on the rather heavy hit to download "the entire layer index database" from the OE instance (and save time getting your "own" layerindex up and running).

Another use of such a list of desired layers might be useful to create a dump from an existing layerindex instance...

Comment 5 Piotr Buliński 2025-10-02 15:24:24 UTC

I like the idea! I’ll see if I can do that tomorrow.