Yocto layer source as tar.gz archive

[amfern]

repos:
  poky:
    url: https://git.yoctoproject.org/poky.git
    tag: yocto-5.1.1
    commit: 7e081bd98fdc5435e850d1df79a5e0f1e30293d0

Kas allows us to use Git repositories for Yocto layers, but I find myself needing to download some Yocto layers as .tar.gz archives instead. (eg. qualcomm blobs)

Is it possible to support Yocto layer sources other than Git repositories?

[fmoessbauer]

Hi, I'm not against it. This could be integrated into the Repo class. However, the repo-class refactoring regarding command string vs. who executes the command should be done first (currently the specializations return commands instead of executing them). After that, we just need another class.

I'm not sure when I will be able to do the refactoring. But patches / help are always welcome. Just send them to the ML.

[jan-kiszka]

Ack, this will need quite some refactoring, I guess, to model the fundamental differences appropriately and also come up with some some, likely, sha256 hash for integrity protection when fetching from remote. We are happy to guide, but it will need a driver here.

[jan-kiszka]

...or motivate Qualcomm to contribute this 😉 . We could possibly arrange some contacts.

[amfern]

I can't promise i have the time to drive it, but it's good to hear your are open for it.

[ndechesne]

I find myself needing to download some Yocto layers as .tar.gz archives instead. (eg. qualcomm blobs)

it's a side question, but can you please describe your qualcomm blob use case?

[amfern]

@ndechesne well qualcomm or some other vendors would often drop us a tar.gz file with all the BSP support.
Which can't be easily fetched by KAS, so i have to pre-fetch and extract before running the KAS build.

[jan-kiszka]

Seems this case is rather uncommon from what I heard. @amfern if you can share an official link by some vendor where they do it the tar-way, that may motivate better.