From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>,
"Frank Ch. Eigler" <fche@elastic.org>
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: install mpfr-dev package on sourceware
Date: Sat, 07 Jan 2023 16:05:48 +0100 [thread overview]
Message-ID: <00dfa3cd4404ec84cb29c7040f3caf3e895f0a61.camel@klomp.org> (raw)
In-Reply-To: <Y7l3XHgsEtJz3MMp@adacore.com>
Hi,
On Sat, 2023-01-07 at 17:45 +0400, Joel Brobecker via Overseers wrote:
> >
> > OTOH even running configure/make should not
> > really be necessary: have y'all considered building the tarballs
> > via "git archive" or such?
>
> This is a good question. The current process is really aweful
> and prone to breaking (all the time, actually). The problem
> is that this process predates me, and I don't have information
> on why it is what it is today. One of the reasons might be that
> it allows pre-generating some files so users of the snapshot
> don't have to.
Yeah, various packages do want to generate some files for their dist
tars. Same for elfutils and binutils. Also some documentation might
need to be (re)generated.
I am working on a sourceware snapshot/docs service using the sourceware
buildbot so you can simply configure a container with the needed
build/dist/doc dependencies. The snapshot process can then run inside
that container (possibly on a separate snapshot build machine).
Currently working on the binutils release script, which should automate
a couple of steps which are now only done by hand at release time. It
should make sure the release process doesn't accidentially break and
you only notice at the time you are preparing an official release.
Cheers,
Mark
prev parent reply other threads:[~2023-01-07 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 12:47 Joel Brobecker
2023-01-07 13:14 ` Frank Ch. Eigler
2023-01-07 13:45 ` Joel Brobecker
2023-01-07 15:05 ` Mark Wielaard [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=00dfa3cd4404ec84cb29c7040f3caf3e895f0a61.camel@klomp.org \
--to=mark@klomp.org \
--cc=brobecker@adacore.com \
--cc=fche@elastic.org \
--cc=overseers@sourceware.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).