List for cgit developers and users
 help / color / mirror / Atom feed
* Fwd: groff-1.23.0.rc4 - no ./configure?
       [not found]   ` <7f1e5e38-be73-c0b9-82be-f39f55a46626@gmail.com>
@ 2023-04-24 22:26     ` Alejandro Colomar
  2023-04-24 23:35     ` Alejandro Colomar
  1 sibling, 0 replies; 3+ messages in thread
From: Alejandro Colomar @ 2023-04-24 22:26 UTC (permalink / raw)
  To: cgit, Jason A. Donenfeld

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: groff-1.23.0.rc4 - no ./configure?
       [not found]   ` <7f1e5e38-be73-c0b9-82be-f39f55a46626@gmail.com>
  2023-04-24 22:26     ` Fwd: groff-1.23.0.rc4 - no ./configure? Alejandro Colomar
@ 2023-04-24 23:35     ` Alejandro Colomar
       [not found]       ` <20230424235109.u3nto6bh3zlbudx6@illithid>
  1 sibling, 1 reply; 3+ messages in thread
From: Alejandro Colomar @ 2023-04-24 23:35 UTC (permalink / raw)
  To: G. Branden Robinson; +Cc: groff mailing list, cgit, Oliver Corff



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
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: groff-1.23.0.rc4 - no ./configure?
       [not found]       ` <20230424235109.u3nto6bh3zlbudx6@illithid>
@ 2023-04-25 10:32         ` Alejandro Colomar
  0 siblings, 0 replies; 3+ messages in thread
From: Alejandro Colomar @ 2023-04-25 10:32 UTC (permalink / raw)
  To: G. Branden Robinson
  Cc: groff mailing list, cgit, Oliver Corff, Jason A. Donenfeld, list+cgit

Since cgit's list is subscribers-only, I've CCd its maintainer.
Also CCd cgit-pink (I hope this one is not subscriber-only).

On 4/25/23 01:51, G. Branden Robinson wrote:
> At 2023-04-25T01:35:03+0200, Alejandro Colomar wrote:
>>> 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).
> 
> It's complicated, and has come up before[1].  I used to try to support
> the cgit-constructed tarballs but it was too much support effort.
> 
> A big part of the problem is that whatever assembles the archives
> doesn't pay attention to git submodules.  One of the most important
> differences between a cgit-generated archive from the groff repo and a
> distribution archive prepared by the maintainer is that the latter
> includes the gnulib sources.  (Including the stuff that "make dist"
> constructs for inclusion in the archive is the other important element.)
> 
> Regards,
> Branden
> 
> [1] This is just one thread of several.
> 
>     https://lists.gnu.org/archive/html/groff/2022-07/msg00064.html

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-04-25 10:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [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: groff-1.23.0.rc4 - no ./configure? Alejandro Colomar
2023-04-24 23:35     ` Alejandro Colomar
     [not found]       ` <20230424235109.u3nto6bh3zlbudx6@illithid>
2023-04-25 10:32         ` Alejandro Colomar

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).