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>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
list+cgit@causal.agency
Subject: Re: groff-1.23.0.rc4 - no ./configure?
Date: Tue, 25 Apr 2023 12:32:19 +0200 [thread overview]
Message-ID: <a790a5ab-6e51-223a-c73b-e3cf7f5601fb@gmail.com> (raw)
In-Reply-To: <20230424235109.u3nto6bh3zlbudx6@illithid>
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
prev parent reply other threads:[~2023-04-25 10:32 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
[not found] ` <20230424235109.u3nto6bh3zlbudx6@illithid>
2023-04-25 10:32 ` Alejandro Colomar [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=a790a5ab-6e51-223a-c73b-e3cf7f5601fb@gmail.com \
--to=alx.manpages@gmail.com \
--cc=Jason@zx2c4.com \
--cc=cgit@lists.zx2c4.com \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--cc=list+cgit@causal.agency \
--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).