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>
Subject: Re: groff-1.23.0.rc4 - no ./configure?
Date: Tue, 25 Apr 2023 01:35:03 +0200 [thread overview]
Message-ID: <c57871ee-a5ad-b936-747e-1ca289f0670a@gmail.com> (raw)
In-Reply-To: <7f1e5e38-be73-c0b9-82be-f39f55a46626@gmail.com>
On 4/25/23 00:25, Alejandro Colomar wrote:
> [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 ?
Probably not. My guess is that cgit just calls git-archive(1).
>
> 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
>
next prev parent reply other threads:[~2023-04-24 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2b5c5ec1-c432-fa3e-8880-bc59ae04e0f4@email.de>
[not found] ` <20230424221409.62yozpbcqfzoptjs@illithid>
[not found] ` <7f1e5e38-be73-c0b9-82be-f39f55a46626@gmail.com>
2023-04-24 22:26 ` Fwd: " Alejandro Colomar
2023-04-24 23:35 ` Alejandro Colomar [this message]
[not found] ` <20230424235109.u3nto6bh3zlbudx6@illithid>
2023-04-25 10:32 ` Alejandro Colomar
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=c57871ee-a5ad-b936-747e-1ca289f0670a@gmail.com \
--to=alx.manpages@gmail.com \
--cc=cgit@lists.zx2c4.com \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--cc=oliver.corff@email.de \
/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 NNTP newsgroup(s).