On 2022-11-13 21:17:29 (+0100), Jelle van der Waa wrote: > https://sources.archlinux.org/sources/$pkgbase/whatever.tar.gz > > They are versioned, example: > > -rw-r--r-- 1 sourceballs sourceballs 49M May 22 13:42 > zynaddsubfx-3.0.6-3.src.tar.gz
> So I never said I wanted the archive in a Git repo, it might be > required for search but that's the next step. So for now binary > sources are just as normal as source tarballs. I see. I guess I misunderstood this, as you brought up the search tooling (which is super helpful btw and I often use your hound to search for things in PKGBUILDs). > I am not sure if this fits into repod and should. However, I'm happy > to discuss it in the next meeting, when is it? As mentioned in my last mail, the source tarball consumption feature is pretty much on the backburner at the moment. However, if we indeed have our build infrastructure/ build tooling generate the source tarballs in the future, we'll eventually want to tackle consumption of these artifacts I guess. Exposing the source tarballs of the current repository packages (as outlined in your examples above) could easily be a configurable thing (like many other features [1]). The next meeting is next week Wednesday [2]. Best, David [1] https://repod.archlinux.page/repod/man/repod_conf.html [2] https://lists.archlinux.org/archives/list/arch-proje...@lists.archlinux.org/thread/BQFBH33YG3IDPFZKU3ERTITUB6GE3ZLD/ -- https://sleepmap.de
signature.asc
Description: PGP signature
