From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: ende.tan@starfivetech.com
Cc: smueller@chronox.de, fontaine.fabrice@gmail.com,
thomas.petazzoni@bootlin.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [1/1] package/libkcapi: update site path
Date: Wed, 21 Aug 2024 09:29:15 +0200 [thread overview]
Message-ID: <ZsWXS9upE8YJCv8I@landeda> (raw)
In-Reply-To: <20240821055146.46029-1-ende.tan@starfivetech.com>
En De, All,
Thanks for this patch.
On 2024-08-21 13:51 +0800, ende.tan@starfivetech.com spake thusly:
> From: Tan En De <ende.tan@starfivetech.com>
>
> Update the site path to reflect the recent organizational changes on the
> chronox.de website.
The way they reorganised the releases is a bit annoying. Indeed, only
the latest release is available with the new URL format, while older
releases are all only available with another format, e.g.:
http://www.chronox.de/libkcapi/releases/1.5.0/libkcapi-1.5.0.tar.xz
http://www.chronox.de/libkcapi/releases/historic/libkcap-1.4.0.tqr.xz
This is annoying, because t means the URL we use is wrong as soon as a
newer release is cut and published, and thus all previous Buildroot
versions suddenly stop being able to download the libkcapi version they
knew about...
I would suggest we switch to using their GitHub repo as the source, and
using git for the download.
> Fixes:
> - http://autobuild.buildroot.org/results/77243633783ac2d037d15d7e9c01384781fe700e
>
> Signed-off-by: Tan En De <ende.tan@starfivetech.com>
In the meantime, applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/libkcapi/libkcapi.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/libkcapi/libkcapi.mk b/package/libkcapi/libkcapi.mk
> index 11462d6e2a..7a79dd55ae 100644
> --- a/package/libkcapi/libkcapi.mk
> +++ b/package/libkcapi/libkcapi.mk
> @@ -6,7 +6,7 @@
>
> LIBKCAPI_VERSION = 1.5.0
> LIBKCAPI_SOURCE = libkcapi-$(LIBKCAPI_VERSION).tar.xz
> -LIBKCAPI_SITE = http://www.chronox.de/libkcapi
> +LIBKCAPI_SITE = http://www.chronox.de/libkcapi/releases/$(LIBKCAPI_VERSION)
> LIBKCAPI_AUTORECONF = YES
> LIBKCAPI_INSTALL_STAGING = YES
> LIBKCAPI_LICENSE = BSD-3-Clause (library), BSD-3-Clause or GPL-2.0 (programs)
> --
> 2.34.1
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-21 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 5:51 [Buildroot] [1/1] package/libkcapi: update site path ende.tan
2024-08-21 7:29 ` Yann E. MORIN [this message]
[not found] ` <2437694.qtHMqo9rXr@tauon.atsec.com>
2024-08-21 9:06 ` Yann E. MORIN
[not found] ` <22321294.h8k6rc2Cxg@tauon.atsec.com>
2024-08-21 11:15 ` Yann E. MORIN
[not found] ` <2443170.9o76ZdvQCi@positron.chronox.de>
2024-08-21 12:27 ` Yann E. MORIN
2024-09-18 11:15 ` Peter Korsgaard
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=ZsWXS9upE8YJCv8I@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=ende.tan@starfivetech.com \
--cc=fontaine.fabrice@gmail.com \
--cc=smueller@chronox.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