On Tue, Aug 21, 2012 at 12:55 AM, Peter Johansson wrote:
> On 08/21/2012 02:46 PM, Jason Eisner wrote:
>
>> Better idea:
>>
>> Have default 644 for files and 755 for directories, but let the user
>> override this by explicitly specifying any of
>> * the desir
On Fri, Aug 10, 2012 at 8:43 AM, Jason Eisner wrote:
> The only ways I can see to make it consistent between files and
> directories are to use the "OR" solution for both, or to ignore umask by
> default but have a command-line flag on "sudo make install" that sa
On Fri, Aug 10, 2012 at 5:47 AM, Stefano Lattarini <
stefano.lattar...@gmail.com> wrote:
> This is something to consider carefully though, and only to be changed (if
> we decide to change it) in the next major automake version. For now, we
> should content ourselves with the documentation fix you
Dear Stefano - Thanks very much for your sympathetic reply on the directory
permissions issue. As we haven't heard back further after a few days, I'd
suggest going forward with plan 2.
You found that plan 2 was formerly proposed at <
http://lists.gnu.org/archive/html/bug-automake/2003-05/msg00011.
Followup -- see this thread from 2004:
http://www.digipedia.pl/usenet/thread/16496/9413/
Looks like at one point, someone fixed this problem in the way I
suggested. But then a user on that thread found directory permissions of
755 too restrictive, which may have gotten the fix removed.
One w
Hi automake folks,
There are many, many generic and specific installation guides that tell you
to type something like
./configure && make && sudo make install
and I've been typing that for years.
Unfortunately, when installing OpenFST, I just discovered that the "sudo
make install" part doe
