[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: chown xxx.yyy, POSIX, and LSB
From: |
Jim Meyering |
Subject: |
Re: chown xxx.yyy, POSIX, and LSB |
Date: |
Mon, 23 Feb 2004 21:25:02 +0100 |
Tim Waugh <address@hidden> wrote:
> On Mon, Feb 23, 2004 at 02:42:58PM -0500, Paul Jarc wrote:
>
>> Jim Meyering <address@hidden> wrote:
>> >> /* If there is no colon, then see if there's a `.'. */
>> >> - if (separator == NULL && posix2_version () < 200112)
>> >> + if (separator == NULL && (posix2_version () < 200112 ||
>> >> + !getenv ("POSIXLY_CORRECT")))
>> >
>> > Please consider using a different environment variable.
>> > Setting POSIXLY_CORRECT should not make an otherwise-POSIX-conforming
>> > program like GNU chown *non*conforming.
>>
>> Setting the variable would mean that "." *wouldn't* be recognized,
>> AFAICT. If it's *not* set, then "." is considered as a separator.
>
> Precisely -- this is what I tried to say in words, and then with the
> code. :-)
Oh. I see now.
If you do that, you should also adjust `chown --help' output
and coreutils.texi to describe the new default behavior.
You should also change the descriptions of the
--from=CURRENT_OWNER:CURRENT_GROUP
option, since it too relies on the parse_user_spec function
that you're proposing to change.
- chown xxx.yyy, POSIX, and LSB, Tim Waugh, 2004/02/23
- Re: chown xxx.yyy, POSIX, and LSB, Jim Meyering, 2004/02/23
- Re: chown xxx.yyy, POSIX, and LSB, Tim Waugh, 2004/02/23
- Re: chown xxx.yyy, POSIX, and LSB, Jim Meyering, 2004/02/23
- Re: chown xxx.yyy, POSIX, and LSB, Paul Jarc, 2004/02/23
- Re: chown xxx.yyy, POSIX, and LSB, Tim Waugh, 2004/02/23
- Re: chown xxx.yyy, POSIX, and LSB,
Jim Meyering <=
- Re: chown xxx.yyy, POSIX, and LSB, Paul Eggert, 2004/02/23