Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Weisser, Pascal.ext" <Pascal.Weisser.ext@karlstorz.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Add HOMEPAGE variable to several recipes.
Date: Thu, 11 Dec 2025 06:29:03 -0800	[thread overview]
Message-ID: <120671.1765463343248308488@lists.openembedded.org> (raw)
In-Reply-To: <952C109B-6A6C-4388-B937-6200BFE718E1@arm.com>

[-- Attachment #1: Type: text/plain, Size: 788 bytes --]

There are several reasons for this change:

First, according to the recipe style guide, HOMEPAGE is a required variable and should be contained in all recipes:

https://docs.yoctoproject.org/dev/contributor-guide/recipe-style-guide.html#required-variables

Second, the recipe linter oelint-adv also wants HOMEPAGE to be set.

Third, the HOMEPAGE is included in the SBOM if it is set. It would be great, if every component would contain the HOMEPAGE to be consistent.

I checked what other recipes are doing when they just provide local files. The recipes mini-x-session or python3-dtschema-wrapper also set HOMEPAGE to "https://yoctoproject.org", so I thought that would be the accepted way to have a HOMEPAGE for recipes that only provide local files.

Best regards
Pascal

[-- Attachment #2: Type: text/html, Size: 1118 bytes --]

  reply	other threads:[~2025-12-11 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09 13:22 [PATCH 0/3] Add HOMEPAGE variable to several recipes Weisser, Pascal
2025-12-09 13:22 ` [PATCH 1/3] ssh-pregen-hostkeys: Add HOMEPAGE variable Weisser, Pascal
2025-12-09 13:22 ` [PATCH 2/3] weston-init: " Weisser, Pascal
2025-12-09 13:22 ` [PATCH 3/3] keymaps: " Weisser, Pascal
2025-12-11 10:29 ` [OE-core] [PATCH 0/3] Add HOMEPAGE variable to several recipes Quentin Schulz
2025-12-11 11:05   ` Ross Burton
2025-12-11 14:29     ` Weisser, Pascal.ext [this message]
2025-12-11 15:19       ` Alexander Kanavin
2025-12-11 18:13         ` Peter Kjellerstedt

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=120671.1765463343248308488@lists.openembedded.org \
    --to=pascal.weisser.ext@karlstorz.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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