From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
---|---|
To: | Karel Zak - Zakkr <zakkr(at)zf(dot)jcu(dot)cz> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] pg_dump --help |
Date: | 1999-12-16 12:23:00 |
Message-ID: | Pine.GSO.4.02A.9912161316180.18547-100000@Utter.DoCS.UU.SE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 15 Dec 1999, Karel Zak - Zakkr wrote:
> $ pg_dump --help
> /usr/lib/postgresql/bin/pg_dump: invalid option -- -
>
> hmm ?
>
> Prepare anyone long options for pg_dump, pg_passwd, pg_version ?
> If not, I make it, current state is disgraceful.
Only GNU (Linux) systems support long options. What you consider
disgraceful is normal behavior on the majority of platforms.
I put in long options into psql and into the wrapper scripts (under some
protests). But I agree that we should if at all only provide them, not
advertise them, since it's going to be a support nightmare.
If you plan on doing this, please look there and use the same options
whereever possible. I have been trying to establish some consistent
options naming across client applications. Also check out how psql copes
with systems where there are no long options available.
Meanwhile I have been getting closer to resolving to scratch pg_dump and
write a new one for 7.1, so whatever you do now might not live long. :(
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak - Zakkr | 1999-12-16 12:45:01 | Re: [HACKERS] pg_dump --help |
Previous Message | Peter Eisentraut | 1999-12-16 12:14:59 | Re: [HACKERS] initdb / pg_version |