Hi Eric, Right now there exists index.json[1] and we might want to create something like manifest.json, too. This way I’d be package manger format independent and would allow downstream tools to digest our existing packages.
Best, Paul [1]: https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/base/index.json > On 9. Nov 2024, at 17:28, Eric <evil.funct...@proton.me> wrote: > > On Saturday, November 9th, 2024 at 07:50, Paul Spooren <m...@aparcar.org> > wrote: > >> My self hosted infrastructure is obsolete and we moved instead to the >> official staging environment1. >> > > Hi Paul, > > I'm looking at the binary database "packages.adb"[1] on the staging server, > where on the production server we have the ascii "Packages"[2] file, which > lists all of the package info. Since the ASU server does its own parsing of > [2] in the `parse_packages_file` function, are we going to have the build do > a translation step to make an equivalent "Packages" or should we add code to > the ASU server to use the new "packages.adb" for that? > > Eric > > [1] > https://downloads.staging.openwrt.org/snapshots/targets/x86/64/packages/packages.adb > [2] https://downloads.openwrt.org/snapshots/targets/x86/64/packages/Packages
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
