From: Jack Nagel <jacknagel@gmail.com>
To: discuss@mdocml.bsd.lv
Subject: Re: File permission issue in recent tarballs?
Date: Fri, 1 Jul 2011 16:49:19 -0500 [thread overview]
Message-ID: <BANLkTi=HwfgkOaWEFV=0ddnLiv=w6ANc=w@mail.gmail.com> (raw)
In-Reply-To: <4E0D87D0.2040606@bsd.lv>
Sounds good. Thanks for the help.
Jack
On Fri, Jul 1, 2011 at 3:39 AM, Kristaps Dzonsons <kristaps@bsd.lv> wrote:
>> The files in the current (1.11.3) tarball are not owner-writeable.
>>
>> Read-only files make it difficult for things like package management
>> software to edit the installation prefix, apply patches, etc.
>>
>> The change appears to have occurred between 1.10.9 and 1.11.1. Here
>> are a couple of excerpts from freshly untarred directory listings:
>>
>> [jacknagel@yonah mdocml-1.10.9]$ ls -la
>> ...
>> -rw-r--r--@ 1 jacknagel staff 9560 Jan 7 09:07 Makefile
>> -rw-r--r--@ 1 jacknagel staff 1141 Jan 7 09:07 arch.c
>> -rw-r--r--@ 1 jacknagel staff 1868 Jan 7 09:07 arch.in
>> -rw-r--r--@ 1 jacknagel staff 1138 Jan 7 09:07 att.c
>>
>>
>> [jacknagel@yonah mdocml-1.11.1]$ ls -la
>> ...
>> -r--r--r--@ 1 jacknagel staff 8649 Apr 4 17:07 Makefile
>> -r--r--r--@ 1 jacknagel staff 1159 Apr 4 17:07 arch.c
>> -r--r--r--@ 1 jacknagel staff 1868 Apr 4 17:07 arch.in
>> -r--r--r--@ 1 jacknagel staff 1156 Apr 4 17:07 att.c
>>
>> Thanks.
>
> Hi Jack,
>
> I'm ambivalent to this (the change was in 1.319, with the Makefile
> re-write), so can patch for the next release. Any objections from
> downstream before I do so?
>
> Kristaps
>
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-07-01 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 21:05 Jack Nagel
2011-07-01 8:39 ` Kristaps Dzonsons
2011-07-01 21:49 ` Jack Nagel [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='BANLkTi=HwfgkOaWEFV=0ddnLiv=w6ANc=w@mail.gmail.com' \
--to=jacknagel@gmail.com \
--cc=discuss@mdocml.bsd.lv \
/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).