From: Mark Wielaard <mark@klomp.org>
To: Nick Clifton <nickc@redhat.com>
Cc: joel@rtems.org, Mike Frysinger <vapier@gentoo.org>,
Joel Brobecker <brobecker@adacore.com>,
Binutils <binutils@sourceware.org>
Subject: Re: A GNU Binutils wiki
Date: Sat, 31 Dec 2022 23:19:55 +0100 [thread overview]
Message-ID: <Y7C1i5cZM26N2s1A@wildebeest.org> (raw)
In-Reply-To: <4944644e-68c3-abfa-e2dd-e99bcb4085f0@redhat.com>
Hi Nick,
On Wed, Nov 30, 2022 at 11:03:12AM +0000, Nick Clifton via Binutils wrote:
> > How are the current code snapshots created?
>
> I think that there is a cron job on sourceware that creates the snapshots.
I can find the gdbadmin cron job that creates gdb snapshots, but it
looks like you create the binutils snapshots by hand and upload them
to https://sourceware.org/pub/binutils/snapshots/
It would be nice to automate this a bit more either with a real
cronjob or a specific buildbot worker.
> > How is the documentation uploaded at release time?
>
> By hand. :-)
>
> I have a procedure outlined in the binutils/README-how-to-make-a-release
> document that I follow whenever I need to update the documentation.
Nice. I saw you just updated for the next release. We can automate
some steps of that. Specifically 9. Create an initial
pre-release. Which can be a build script for the buildbot that can
create a snapshot each commit or day.
About
12. Build various different toolchains, test them and nag
maintainers to fix any testsuite failures for their
architectures...
Which toolchains/architectures are that? Are any of them missing from:
https://builder.sourceware.org/buildbot/#/builders?tags=binutils
BTW. binutils-debian-i386, binutils-fedora-arm64 and
binutils-fedora-s390x do show some testsuite failures.
> > We can automate both and publish them on a special buildbot worker
> > under something like snapshots.sourceware.org/bintuils to keep them
> > current and so everybody can immediately see how the documentation
> > looks.
>
> That would be nice. Would it involve taking up a lot of disk space ?
> (Ie for how long would these snapshots last ?)
binutils snapshots are ~24MB, documentation ~18MB. So if we do one a
day that is ~1GB a month. And since it looks like you recently added
the option to create reproducible tarballs we don't really need to
keep all of them since people could recreate them from a git checkout.
Cheers,
Mark
next prev parent reply other threads:[~2022-12-31 22:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 13:34 Nick Clifton
2022-11-01 13:44 ` Joel Brobecker
2022-11-01 15:17 ` Mike Frysinger
2022-11-01 16:47 ` Nick Clifton
2022-11-02 10:34 ` Mike Frysinger
2022-11-02 13:41 ` Joel Sherrill
2022-11-02 14:49 ` Nick Clifton
2022-11-02 15:04 ` Joel Brobecker
2022-11-02 15:12 ` Joel Sherrill
2022-11-27 23:44 ` Mark Wielaard
2022-11-30 11:03 ` Nick Clifton
2022-12-31 22:19 ` Mark Wielaard [this message]
2023-01-03 10:08 ` Nick Clifton
2022-11-02 15:28 ` Luis Machado
2022-11-09 17:00 ` Mike Frysinger
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=Y7C1i5cZM26N2s1A@wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=joel@rtems.org \
--cc=nickc@redhat.com \
--cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).