Fwd: groff-1.23.0.rc4 - no ./configure?

[Alejandro Colomar <alx.manpages@gmail.com>]

Let's see if I had this email subscribed.


-------- Forwarded Message --------
Subject: Re: groff-1.23.0.rc4 - no ./configure?
Date: Tue, 25 Apr 2023 00:25:14 +0200
From: Alejandro Colomar <alx.manpages@gmail.com>
To: G. Branden Robinson <g.branden.robinson@gmail.com>
CC: groff mailing list <groff@gnu.org>, cgit@lists.zx2c4.com, Oliver Corff <oliver.corff@email.de>

[CC += CGit]

Hi Branden!

On 4/25/23 00:14, G. Branden Robinson wrote:
> Hi Oliver,
> 
> At 2023-04-24T22:40:23+0200, Oliver Corff wrote:
>> I went to https://git.savannah.gnu.org/cgit/groff.git today to
>> download the rc4 tarball groff-1.23.0.rc4.tar.gz and unpacked the
>> archive.
> 
> I've made the same mistake myself!
> 
> The official distribution archives are not available via the cgit
> interface.  cgit doesn't know about FSF deployment procedures and hasn't
> been taught.

Curious way to put it.  I wondered something along those lines recently:
Is it possible to teach cgit how to create a tarball?  It would be nice
if I just made a tag and cgit would do the automated process necessary
for the tarball.

Moreover, I considered not releasing tarballs anymore as a possibility,
since one can produce them following some repeatable command.

Would I be able to teach cgit to run

    $ make dist-gz

And then find the tarball in ./.tmp/$(git describe).tar.gz ?

Cheers,
Alex

> 
> As noted in the RC announcement email[1], you need to get the
> distribution archive from the alpha.gnu.org website.
> 
>   https://alpha.gnu.org/gnu/groff/
> 
>> How do I configure the makefile? I fail to see a ./configure script.
> 
> Carlos's response here was correct--you have to use the INSTALL.REPO
> instructions if you want to build from the Git repository--but if you
> want to provide feedback on the release candidate, then that's not the
> procedure to follow.
> 
> Regards,
> Branden
> 
> [1] https://lists.gnu.org/archive/html/groff/2023-04/msg00135.html

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5