From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Mark Wielaard <mark@klomp.org>
Cc: buildbot@sourceware.org, binutils@sourceware.org,
Nick Clifton <nickc@redhat.com>,
elena.zannoni@oracle.com, david.faust@oracle.com
Subject: Re: binutils snapshot builds
Date: Thu, 23 May 2024 17:11:40 +0200 [thread overview]
Message-ID: <87y180mukz.fsf@oracle.com> (raw)
In-Reply-To: <20240522221523.458943-1-mark@klomp.org> (Mark Wielaard's message of "Thu, 23 May 2024 00:08:51 +0200")
Hi Mark.
Thanks for doing this!
I see that the name of the snapshot tarball for a version
m4_define([BFD_VERSION], [2.42.50-fc12b44ec0e])
is
binutils-2.42.50.tar.gz
What about having:
binutils-2.42.50-fc12b44ec0e.tar.gz
This would allow for example to easily cache already downloaded
snapshots on the client side.
Also, would it be possible to have a file README (or LATEST or MANIFEST
or whatever) in the directory with a single line containing the name of
the tarball? This would ease automation.
WDYT?
> The following two patches implement binutils snapshots for
> https://snapshots.sourceware.org/
>
> [PATCH 1/2] Add binutils-snapshots builder
> [PATCH 2/2] binutils snapshot steps should run in the git step
>
> Sorry about the second patch, I pushed the first before realizing I
> got the directory wrong.
>
> This really is just two commands:
>
> sed -i "s/m4_define(\[BFD_VERSION\],
> \[\([0-9\\.]\+\)\])/m4_define(\[BFD_VERSION\], [\1-$(git rev-parse
> --short @)])/" bfd/version.m4
>
> To make the version unique.
>
> ./src-release.sh -g binutils
>
> To create a binutils tar.gz release tarball.
>
> This is then put up on:
>
> https://snapshots.sourceware.org/binutils/trunk/
>
> It gets regenerated every 15 minutes, if there have been any changes
> since the last build. The latest can always be found here:
>
> https://snapshots.sourceware.org/binutils/trunk/latest/src/
>
> Cheers,
>
> Mark
next prev parent reply other threads:[~2024-05-23 15:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 22:08 Mark Wielaard
2024-05-22 22:08 ` [PATCH 1/2] Add binutils-snapshots builder Mark Wielaard
2024-05-22 22:08 ` [PATCH 2/2] binutils snapshot steps should run in the git step workdir Mark Wielaard
2024-05-23 8:57 ` binutils snapshot builds Frank Scheiner
2024-05-23 11:36 ` Andreas Schwab
2024-05-23 13:30 ` Frank Scheiner
2024-05-23 23:15 ` Mark Wielaard
2024-05-23 23:37 ` Sam James
2024-05-24 0:16 ` Mark Wielaard
2024-05-24 0:27 ` Sam James
2024-05-25 17:40 ` Frank Scheiner
2024-05-26 0:31 ` Mark Wielaard
2024-05-27 18:14 ` Frank Scheiner
2024-05-23 10:35 ` Nick Clifton
2024-05-23 23:32 ` Mark Wielaard
2024-05-24 12:31 ` Nick Clifton
2024-05-24 14:03 ` Jose E. Marchesi
2024-05-23 15:11 ` Jose E. Marchesi [this message]
2024-05-23 15:28 ` Frank Ch. Eigler
2024-05-23 15:33 ` Jose E. Marchesi
2024-05-23 22:52 ` Sam James
2024-05-23 23:59 ` Mark Wielaard
2024-05-23 23:41 ` Mark Wielaard
2024-05-24 9:58 ` Jose E. Marchesi
2024-05-26 0:16 ` Mark Wielaard
2024-05-28 14:35 ` Nick Clifton
2024-05-28 16:16 ` Mark Wielaard
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=87y180mukz.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=binutils@sourceware.org \
--cc=buildbot@sourceware.org \
--cc=david.faust@oracle.com \
--cc=elena.zannoni@oracle.com \
--cc=mark@klomp.org \
--cc=nickc@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).