From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>,
Christian Stewart <christian@aperture.us>,
Marcus Folkesson <marcus.folkesson@gmail.com>
Subject: Re: [Buildroot] [PATCH 2/6] package/libcamera-apps: fix LIBCAMERA_APPS_VERSION
Date: Mon, 29 Dec 2025 18:08:39 +0100 [thread overview]
Message-ID: <20251229180839.07da40f2@windsurf> (raw)
In-Reply-To: <20250926100609.4158676-2-dario.binacchi@amarulasolutions.com>
On Fri, 26 Sep 2025 12:06:05 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:
> -LIBCAMERA_APPS_VERSION = v1.7.0-10-ge9645231008146fa0e75c2b3e0ff8c48ad70511a
> -LIBCAMERA_APPS_SITE = $(call github,raspberrypi,rpicam-apps,$(LIBCAMERA_APPS_VERSION))
> +LIBCAMERA_APPS_VERSION = 1.7.0-10-ge9645231008146fa0e75c2b3e0ff8c48ad70511a
> +LIBCAMERA_APPS_SITE = $(call github,raspberrypi,rpicam-apps,v$(LIBCAMERA_APPS_VERSION))
While for embiggen-disk your patch was definitely useful, here I don't
see the point, because
1.7.0-10-ge9645231008146fa0e75c2b3e0ff8c48ad70511a still doesn't match
anything relevant on release-monitoring.org.
I'm not sure how to address this.
Option 1 is:
LIBCAMERA_APPS_VERSION = 1.7.0
LIBCAMERA_APPS_SITE = $(call github,raspberrypi,rpicam-apps,v$(LIBCAMERA_APPS_VERSION)-10-ge9645231008146fa0e75c2b3e0ff8c48ad70511a)
That's easy, but it means that during the build, the version display
will be just 1.7.0, and the build directory will be named
libcamera-apps-1.7.0, so we're kind of lying to the user here.
The other option is to have a different variable for release-monitoring
lookups, that defaults to <pkg>_VERSION but can be overridden.
Like:
LIBCAMERA_APPS_RM_VERSION = 1.7.0
LIBCAMERA_APPS_VERSION = $(LIBCAMERA_APPS_RM_VERSION)-10-ge9645231008146fa0e75c2b3e0ff8c48ad70511a
Note that aside from that, we also have the case of packages fetched
through Git, for which we cannot currently separate the version from
the "download version", and therefore we do have these vX.Y.Z.
So I think some broader thinking/effort is needed here to solve this.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-12-29 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 10:06 [Buildroot] [PATCH 1/6] package/embiggen-disk: fix EMBIGGEN_DISK_VERSION Dario Binacchi
2025-09-26 10:06 ` [Buildroot] [PATCH 2/6] package/libcamera-apps: fix LIBCAMERA_APPS_VERSION Dario Binacchi
2025-12-29 17:08 ` Thomas Petazzoni via buildroot [this message]
2025-09-26 10:06 ` [Buildroot] [PATCH 3/6] package/libcrossguid: fix LIBCROSSGUID_VERSION Dario Binacchi
2025-09-26 10:06 ` [Buildroot] [PATCH 4/6] package/libesmtp: fix LIBESMTP_VERSION Dario Binacchi
2025-09-26 10:06 ` [Buildroot] [PATCH 5/6] package/mjpg-streamer: fix MJPG_STREAMER_VERSION Dario Binacchi
2025-09-26 10:06 ` [Buildroot] [PATCH 6/6] package/spirv-llvm-translator: fix SPIRV_LLVM_TRANSLATOR_VERSION Dario Binacchi
2025-09-27 6:48 ` [Buildroot] [PATCH 1/6] package/embiggen-disk: fix EMBIGGEN_DISK_VERSION Christian Stewart via buildroot
2025-12-29 16:55 ` Thomas Petazzoni via buildroot
2026-01-13 19:45 ` Arnout Vandecappelle via buildroot
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=20251229180839.07da40f2@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=christian@aperture.us \
--cc=dario.binacchi@amarulasolutions.com \
--cc=marcus.folkesson@gmail.com \
--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