public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/23995] Remove execution flags from localedata/locales/bi_VU
Date: Mon, 17 Dec 2018 21:39:00 -0000	[thread overview]
Message-ID: <bug-23995-716-P47YyxQIIO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23995-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=23995

--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Sun, 16 Dec 2018, pander at users dot sourceforge.net wrote:

> This command also reports that the file
> 
>     timezone/yearistype
> 
> is executable. Looking at the file, the original name was yearistype.sh Perhaps

There is no need for suffixes on executable files, and an argument for not 
having them (the language the program happens to be implemented in is not 
part of its interface - in particular, *installed* programs should not 
have such suffixes).  Some such files need to be run by the makefiles 
explicitly to use the correct interpreter found by configure, in which 
case there is no need for executable bits at all, but that doesn't apply 
when the interpreter is /bin/sh (although maybe yearistype execution by 
zic doesn't actually need the executable bit).  So I don't see any problem 
with yearistype - it's appropriately executable, whether or not the 
execute bit is actually needed, and not having a suffix is fine, whether 
or not having one would also be OK.

Locale data files indeed should not be marked executable.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2018-12-17 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16 15:04 [Bug localedata/23995] New: " pander at users dot sourceforge.net
2018-12-17 21:39 ` joseph at codesourcery dot com [this message]
2018-12-17 22:21 ` [Bug localedata/23995] " pander at users dot sourceforge.net
2018-12-18  9:32 ` fweimer at redhat dot com
2018-12-18  9:57 ` cvs-commit at gcc dot gnu.org
2018-12-18  9:57 ` fweimer at redhat dot com
2018-12-19  9:18 ` pander at users dot sourceforge.net
2019-01-31 17:17 ` cvs-commit at gcc dot gnu.org

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=bug-23995-716-P47YyxQIIO@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@sourceware.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.
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).