public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <quentin.schulz@cherry.de>, <docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 2/2] Makefile: add a releases.json target
Date: Thu, 26 Feb 2026 14:53:28 +0100	[thread overview]
Message-ID: <DGOXZKODG8PH.19EQQELQAPEO3@bootlin.com> (raw)
In-Reply-To: <34206d2c-7f89-45ce-9db2-e363d24e0cb5@cherry.de>

Hi,

On Wed Feb 25, 2026 at 3:10 PM CET, Quentin Schulz via lists.yoctoproject.org wrote:
> Hi Antonin,
>
> Please provide context, what is this helping with?

It's helping when updating this file is needed (but see below).

> On 2/25/26 1:06 PM, Antonin Godard via lists.yoctoproject.org wrote:
>> Add a new releases.json target which can be used to update the
>> releases.json file manually. It is called from the publish target only
>> (which is the one used on the Autobuilder).
>> 
>> A warning is printed when the file is not up-to-date anymore.
>> 
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>>   documentation/Makefile                                      | 9 +++++++--
>>   documentation/tools/host_packages_scripts/almalinux_docs.sh | 2 +-
>>   documentation/tools/host_packages_scripts/fedora_docs.sh    | 2 +-
>>   documentation/tools/host_packages_scripts/opensuse_docs.sh  | 2 +-
>>   documentation/tools/host_packages_scripts/ubuntu_docs.sh    | 2 +-
>>   5 files changed, 11 insertions(+), 6 deletions(-)
>> 
>> diff --git a/documentation/Makefile b/documentation/Makefile
>> index e144a50b4..00c7d957d 100644
>> --- a/documentation/Makefile
>> +++ b/documentation/Makefile
>> @@ -24,9 +24,9 @@ endif
>>   help:
>>   	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
>>   
>> -.PHONY: all checks help Makefile clean stylecheck publish epub latexpdf
>> +.PHONY: all checks help Makefile clean stylecheck publish epub latexpdf releases.json
>>   
>> -publish: Makefile checks epub latexpdf html singlehtml
>> +publish: releases.json Makefile checks epub latexpdf html singlehtml
>>   	rm -rf $(BUILDDIR)/$(DESTDIR)/
>>   	mkdir -p $(BUILDDIR)/$(DESTDIR)/
>>   	cp -r $(BUILDDIR)/html/* $(BUILDDIR)/$(DESTDIR)/
>> @@ -73,6 +73,11 @@ latexpdf: $(PDFs)
>>   	$(SOURCEDIR)/set_versions.py
>>   	buf_size=10000000 $(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
>>   
>> +releases.json:
>> +	command -v curl jq || echo "curl and jq need to be installed for this target"
>> +	curl https://dashboard.yoctoproject.org/releases.json | jq --indent 2 >$(SOURCEDIR)/releases.json
>
> Do we really need jq? What is this bringing? It won't be human-consumed 
> anyway, so who cares for the indent?

Updates to this file would possibly be posted on the list. Having them formatted
make the diffs readable.

> Why do we need to download the file during the publish state? Cannot we 
> make the autobuilder download the file and put it in the right place? 
> This will also avoid the case where the file gets changed while the 
> autobuilder builds one earlier release and the latest one.

That's correct, thanks!

I reconsidered this and opted for a different approach which I'll send shortly.

Antonin


      reply	other threads:[~2026-02-26 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 12:05 [PATCH 0/2] set_versions.py: build with versions from releases.json Antonin Godard
2026-02-25 12:05 ` [PATCH 1/2] " Antonin Godard
2026-02-25 14:15   ` [docs] " Quentin Schulz
2026-02-26 13:56     ` Antonin Godard
2026-02-25 12:06 ` [PATCH 2/2] Makefile: add a releases.json target Antonin Godard
2026-02-25 14:10   ` [docs] " Quentin Schulz
2026-02-26 13:53     ` Antonin Godard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DGOXZKODG8PH.19EQQELQAPEO3@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox