Hi Sebastian, that's correct. We (I mean Nicholas) put this in place during the Hackfest and unfortunately did not document this secret feature anywhere.
Anyhow we should consider maybe creating a GREP for how to handle OOT metadata (and maybe don't store yaml inside of a `*.md` file). So we can actually have some versioning in place, On a parallel track I'm trying to work out how to auto-generate debian source packages (and build them on the CI) for our zoo of OOTs which will hopefully lead to a less source-centric user perspective for GNU Radio. And I will definitely need to have a good access format for OOT metadata, be it MANIFESTs and/or PYBOMBs recipes. I haven't fully figured out yet what would be the "perfect" solution. Cheers Andrej On Fri, 7 Feb 2020 08:14:50 +0100 Sebastian Müller <gse...@gmail.com> wrote: > Hi, > > I “reverse engineered” this this feature. > You should place a “gr_supported_version” key in your MANIFEST. The > value is just a string AFAIK, eg “v3.7, v3.8”. > > Sebastian Müller > > > On 6. Feb 2020, at 20:26, Sylvain Munaut <246...@gmail.com> wrote: > > > > Hi, > > > >> Regarding that column, how does it work? I've seen that only > >> gr-fosphor and gr-iqbal have that column filled out currently, but > >> I don't know how tnt has accomplished that. I don't see anything > >> special in the MANIFEST.md nor in the .lwr recipe. > > > > I accomplished that by not being on github ... and so CGRAN doesn't > > actually even look at my manifest file and the data for fosphor and > > iqbal is literally hard-coded inside of CGRAN's codebase. > > > > Cheers, > > > > Sylvain > > >
pgp37KC3XJ32N.pgp
Description: OpenPGP digital signature
