From: John Kacur <jkacur@redhat.com>
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-rt-users@vger.kernel.org
Subject: Re: rt-tests release tarball location
Date: Wed, 8 Jan 2025 13:17:43 -0500 (EST) [thread overview]
Message-ID: <6569931b-16e5-5965-dfd0-7ffdf80fffab@redhat.com> (raw)
In-Reply-To: <87h66b2c6m.fsf@kurt.kurt.home>
On Tue, 7 Jan 2025, Kurt Kanzenbach wrote:
> On Sat Dec 28 2024, Thomas Petazzoni wrote:
> > Hello,
> >
> > I am one of the co-maintainers of Buildroot, an embedded Linux build
> > system. Among many other packages, we obviously have rt-tests as one of
> > our packages. When rt-tests is built, we download it from kernel.org.
> > Unfortunately, the rt-tests tarballs are moved around: the latest
> > release is available at https://www.kernel.org/pub/linux/utils/rt-tests/,
> > but as soon as another newer release is available, the older release
> > tarballs get moved to
> > https://www.kernel.org/pub/linux/utils/rt-tests/older/.
> >
> > This breaks the build for build systems such as Buildroot, that expect
> > a release tarball to stay at a given location, and not being moved
> > around.
> >
> > Would it possible to keep the tarballs at the same location? Either by
> > not having the older/ folder entirely, or by populating it immediately
> > with the latest release, so that all releases are always available from
> > the older/ folder?
>
> +1
>
> For Gentoo I had to add both URLs to SRC_URI in the ebuilds. It first
> tries rt-tests/ and then rt-tests/older/ location, which is also not
> ideal.
Why is it not ideal? This seems like a perfectly reasonable solution?
John
prev parent reply other threads:[~2025-01-08 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 10:43 rt-tests release tarball location Thomas Petazzoni
2025-01-07 9:41 ` Kurt Kanzenbach
2025-01-07 14:14 ` Sebastian Andrzej Siewior
2025-01-08 18:21 ` John Kacur
2025-01-08 19:05 ` Crystal Wood
2025-01-09 8:05 ` Sebastian Andrzej Siewior
2025-01-09 10:13 ` Tomas Glozar
2025-01-09 10:49 ` Sebastian Andrzej Siewior
2025-01-09 12:04 ` Jörg Sommer
2025-01-10 16:46 ` John Kacur
2025-08-13 21:06 ` Thomas Petazzoni
2025-08-18 19:18 ` John Kacur
2025-08-18 19:24 ` Thomas Petazzoni
2025-01-08 18:17 ` John Kacur [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=6569931b-16e5-5965-dfd0-7ffdf80fffab@redhat.com \
--to=jkacur@redhat.com \
--cc=kurt@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.