I looked into this, ideally I'd like to add the URL since it's nicer, but it's not as straightforward as it seems. See this URL: https://github.com/raspberrypi/rpi-eeprom/releases/download/v2020.04.16-137ad/rpi-boot-eeprom-recovery-2020-04-16-vl805-000137ad.zip

First of all, they are not using the exact same version string on the zip file as the one on the git tag. Not ideal, but I can deal with that.

Secondly their naming scheme doesn't match my package name. I guess that's on me. One thing I could do is rename the package so both match.

Ultimately, they are using zip to package their releases, which AFAIK doesn't play well with spec us.

Any ideas/suggestions?

Note that I'd really like to use the releases, as opposed to getting snapshots of the repo as this is firmware and we have to be extra careful.

Nicolas Patricio Saenz Julienne (nsaenzjulienne) - almost 4 years ago

author target maintainer

s/spec//

Guillaume GARDET (Guillaume_G) - almost 4 years ago

target maintainer

For the version ('.' vs '-'), you can use: %define archive_version 2020-04-16-vl805-000137ad

For the archive, you can use any name you want, just update the %setup section, IIRC, %setup -n XXX, with XXX matching the folder in the archive.

With zip, you need to add 'BuildRequires: unzip'