From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel@gnu.org
Subject: Re: default tar format for "make dist" and patch file length
Date: Wed, 17 Nov 2021 12:32:58 +0100 [thread overview]
Message-ID: <874k8bxbit.fsf@gnu.org> (raw)
In-Reply-To: <87sfvxhrav.fsf@ponder> (Vagrant Cascadian's message of "Mon, 15 Nov 2021 16:34:16 -0800")
Vagrant Cascadian <vagrant@debian.org> skribis:
> Ideally, "guix lint" would be run and issues fixed before applying
> patches ... !
On the bright side, that there’s just a dozen of issues on 20K packages
suggests it’s usually run. :-)
I think we’re used to running it for new packages but not when modifying
an existing package, which is probably when issues like that are
introduced.
> Is it worth adding an inexpensive check to etc/git/pre-push that also
> checks for file-length and fails to push due to this issue potentially
> breaking "make dist"?
Could be.
> A different angle might be to actually use a different tar format:
>
> https://www.gnu.org/software/tar/manual/html_section/Formats.html
>
> I would guess "make dist" is using the tar "v7" format, based on the 99
> character length limit for files. Most of the other formats have no file
> length limit or a longer limit.
Yes, we could also do that.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-11-17 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 0:34 default tar format for "make dist" and patch file length Vagrant Cascadian
2021-11-17 11:32 ` Ludovic Courtès [this message]
2021-11-17 22:39 ` Vagrant Cascadian
2021-11-17 23:49 ` Vagrant Cascadian
2021-11-19 14:54 ` Ludovic Courtès
2021-11-20 4:39 ` Philip McGrath
2021-11-20 5:21 ` Vagrant Cascadian
2021-11-24 21:27 ` Vagrant Cascadian
2021-11-22 2:03 ` Maxim Cournoyer
2021-11-22 11:31 ` Ludovic Courtès
2021-11-22 20:14 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874k8bxbit.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).