Complete.Org: Mailing Lists: Archives: freeciv-dev: August 2000:
[Freeciv-Dev] Re: why is po/POTFILES write protected?
Home

[Freeciv-Dev] Re: why is po/POTFILES write protected?

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: why is po/POTFILES write protected?
From: Jeff Mallatt <jjm@xxxxxxxxxxxx>
Date: Tue, 22 Aug 2000 15:20:02 -0400

At 2000/08/22 14:59 , Thue wrote:
>See title; I can't see why. But it is a little irriting when I do a
>
>rm -r <copy of freeciv> &

Yes, it would be.

On my machine, however, po/POTFILES is 664, so I can rm it just fine.

It is generated by a very simple sed script, with output redirected to the
file (which has first been removed), so nothing fancy is going on.  What
will the umask be when you run ./configure?  If it's something like 222,
then the new po/POTFILES file will be created 444, which could cause your
problem.

jjm




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