Bug#873698: Proposal for a working watch file

2017-11-28 Thread Moritz Schlarb
Hi Christoph, On 28.11.2017 11:02, Christoph Martin wrote: > Hi Moritz, > > if the files are on github you can easily use the following lines: The problem is that the Github "releases" are actually just plain Git tags so the downloadable archives that Github offers are just snapshots of the Git

Bug#873698: Proposal for a working watch file

2017-11-28 Thread Christoph Martin
Hi Moritz, if the files are on github you can easily use the following lines: https://github.com/cfengine/core/releases \ .*/archive/(\d[\d\.]+)\.tar\.(?:gz|bz2|xz) opts="component=masterfiles" https://github.com/cfengine/masterfiles/releases \ .*/archive/(\d[\d\.]+)\.tar\.(?:gz|bz2|xz) Christ

Bug#873698: Proposal for a working watch file

2017-11-28 Thread Moritz Schlarb
Hi everyone, I fiddled around with the CFEngine releases page and gave up on trying to parse the nested JSON stuff because it doesn't seem to be possible anyway, but I resorted to the releases page on GitHub to get release version numbers and then mangling the download URL to their S3 bucket that