After Holger & Alexander talk at OpenWrt Summit I started thinking
about handling feeds in LEDE. Right now we simply point to external
repositories within feeds.conf(.default):
src-git packages https://git.lede-project.org/feed/packages.git
src-git luci https://git.lede-project.org/project/luci.git
src-git routing https://git.lede-project.org/feed/routing.git
src-git telephony https://git.lede-project.org/feed/telephony.git

I see few problems with this solution:

1) No info on used feeds revisions
Problem: When you get an image you can't say which revisions of feeds
were used to build it.
Possible solution: Include some extra file with info about each feed
and used revision

2) No pointing specific revision
Problem: We always use the latest revision of each feed. It's easy to
hit some problem/regression introduced in a feed without an easy way
of tracking it down. You have to guess which was the latest working
Possible solution: Always point specific revision in
feeds.conf.default, e.g. src-git packages
https://git.lede-project.org/feed/packages.git^commithash .
Unfortunately this will require us to update this file over and over.

3) The way of specifying revisions
Problem: This is only possible with manually creating a proper
feeds.conf. I'm wondering if this would make sense to make is somehow
more script friendly? Alexander, Holger: what do you think about this?
Possible solution: Implement solution suggested in problem 2 or maybe
add support for some env variable(s) pointing revision(s)?

I think the problem that really needs solving is the first one. The
rest we can probably just discuss (hint: waiting for your opinions).
Right now it's not possible/easy to rebuild image I got downloaded.
Even if I'm ready to create my own feeds.conf I don't know what
revisions to put there. Also please note this is only an introduction
to have binary reproducible builds.


Lede-dev mailing list

Reply via email to