Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too many arguments! #6

Open
kstrauser opened this issue Apr 19, 2013 · 2 comments
Open

Too many arguments! #6

kstrauser opened this issue Apr 19, 2013 · 2 comments

Comments

@kstrauser
Copy link
Owner

PgDBF has way too many command line options. For every option, there's another corresponding version to turn it off.

Should we have a one-time backward-incompatible release to turn it off? Maybe bump the current release to version 1.0 and make 2.0 the incompatible cleanup? Or maybe this just isn't a big deal and should be left as-is?

Any opinions would be appreciated!

@crashmaster18
Copy link

"PgDBF has way too many command line options. For every option, there's another corresponding version to turn it off."
<...>
Agreed.

"Should we have a one-time backward-incompatible release to turn it off? Maybe bump the current release to version 1.0 and make 2.0 the incompatible cleanup? <...>"

This is a good idea (make this current release 1.0), but if it will take significant development time then forget it and we will live with the 500 cmd line options. ;-)

@kstrauser
Copy link
Owner Author

I'm leaning in that direction.

On Aug 30, 2013, at 10:10 AM, kevinrsalisbury [email protected] wrote:

"PgDBF has way too many command line options. For every option, there's another corresponding version to turn it off."
<...>
Agreed.

"Should we have a one-time backward-incompatible release to turn it off? Maybe bump the current release to version 1.0 and make 2.0 the incompatible cleanup? <...>"

This is a good idea (make this current release 1.0), but if it will take significant development time then forget it and we will live with the 500 cmd line options. ;-)


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants