From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel@gnu.org
Subject: Re: default tar format for "make dist" and patch file length
Date: Sun, 21 Nov 2021 21:03:24 -0500 [thread overview]
Message-ID: <87zgpxaqvn.fsf@gmail.com> (raw)
In-Reply-To: <87fsru8l05.fsf@ponder> (Vagrant Cascadian's message of "Wed, 17 Nov 2021 14:39:38 -0800")
Hello,
[...]
>>> 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.
>
> Struggling to figure out how to do that; seems automake is very inclined
> to use the old format... anyone with sufficient auto* skills to try and
> upgrade the "make dist" to pass one of the newer --format= arguments to
> tar?
Reading the Automake manual (info (automake) List of Automake options) I
stumbled on this:
‘filename-length-max=99’
Abort if file names longer than 99 characters are found during
‘make dist’. Such long file names are generally considered not to
be portable in tarballs. See the ‘tar-v7’ and ‘tar-ustar’ options
below. This option should be used in the top-level ‘Makefile.am’
or as an argument of ‘AM_INIT_AUTOMAKE’ in ‘configure.ac’; it will
be ignored otherwise. It will also be ignored in sub-packages of
nested packages (*note Subpackages::).
This makes me think that Automake is simply configured out of the box to
keep the file names as portable as possible (it doesn't mean it uses
tar-v7 itself, IIUC, though I haven't checked).
Seems a good thing to be as portable as can be, especially since 200
chars patch file names wouldn't look good in the sources anyway ;-).
Thanks,
Maxim
next prev parent reply other threads:[~2021-11-22 2:04 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
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 [this message]
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=87zgpxaqvn.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--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).