bug-ncurses
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: File mode discrepancies between tarball and ncurses-snapshots git re


From: Sven Joachim
Subject: Re: File mode discrepancies between tarball and ncurses-snapshots git repository
Date: Sun, 29 Jan 2023 17:32:23 +0100
User-agent: Gnus/5.13 (Gnus v5.13)

On 2023-01-29 09:33 -0500, Thomas Dickey wrote:

> On Sun, Jan 29, 2023 at 02:42:05PM +0100, Sven Joachim wrote:
>> There are four scripts which are executable in the ncurses-snapshots git
>> repository[1], but not in the tarballs at invisible-island.net.
>
> odd - I don't recall changing this.  But I understand the cause.
>
> For background, the permissions shown in git snapshots are based on
> the initial import from rcs in 2015.  The script which I wrote for
> making the incremental exports doesn't check for permission changes.
>
> The tarballs are directly from rcs, which doesn't store permissions
> in a versioned form - it's just whatever the file-permissions happen
> to be on the archive-file.

Looking at the Debian git repo, these files had been executable in the
tarballs at least since August 2009 (that is where my imports started,
at the time there was no other public VCS for ncurses I could use).

>> I consulted the Debian git repository where I import the weekly
>> tarballs, and apparently the four scripts lost their executable bits in
>> the 20210619 patchlevel.  Obviously ncurses builds fine anyway, but it
>> looks more correct to make these files executable.
>
> It looks odd, but only because the filenames are suffixed with ".sh"
> (which is more of a stylistic thing than anything else).

It looked odd to me because the files have a shebang line which
indicates they could be executed directly, not because of the ".sh"
extension.

Cheers,
       Sven



reply via email to

[Prev in Thread] Current Thread [Next in Thread]