On Tue, Oct 12, 2021 at 3:25 PM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > > So to answer Neal's question: you can use PDC directly, or you can use > fedfind which will talk to PDC for you, plus do a bunch of other stuff, > like the above, and also synthesizing metadata for pre-Pungi 4 stable > releases so you can interact with them via fedfind using the same > interfaces as post-Pungi 4 composes... > > Hanging over all of this is the threat that PDC might go away at some > point, which would be a bit of an inconvenience. In A World Where there > is no PDC, you have to grab the metadata files for composes that still > exist from kojipkgs; there is no record of the metadata for composes > that have been garbage-collected. For stable releases you'd have to > parse whatever metadata you can just out of the actual release tree on > the mirrors. > Maybe it might be worth considering to generating a json blob to put into the mirrored tree? The problem I *actually* have is that we don't have a predictable/reliable name that I can hard-code in to correctly fetch the ISO. We don't generate unversioned links to versioned ISO files, which is where the complication comes from. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
