This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: setup.exe command line options
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- To: keith_starsmeare at yahoo dot co dot uk
- Cc: cygwin-apps at sources dot redhat dot com
- Date: Wed, 23 Jan 2002 17:46:26 -0500
- Subject: Re: setup.exe command line options
- References: <00b301c1a45e$82614b60$81293c3e@Obsession>
Release early and often. Go ahead and publish what you have, against
current CVS. You only need to #ifdef stuff out if it will actually
BREAK something that is currently working. If it's, say, the handler
for an incompletely implemented commandline option, then it won't break
anything (unless someone actually tries to USE that commandline option.)
- in that case, it doesn't need to be #ifdef'ed.
But Robert has the final call, of course.
--Chuck
keith_starsmeare@yahoo.co.uk wrote:
> I've made some progress, but it's still (infuriatingly) not at the stage
> where you can do a whole installation without dialog boxes (no offense -
> they're lovely dialog boxes!), but you can certainly have *fewer* dialog
> boxes!
>
> I'm wondering if I could submit what I have so far, and either leave some
> bits #ifdef'd out (how does the undefined macro
> COMMAND_LINE_OPTIONS_FULLY_IMPLEMENTED sound!?) or just miss those bits out
> completely from my diff.
>
> I was hoping to submit the final fully working diffs, but I'm only working
> in my spare time and everytime I have a look at the latest sources they've
> moved on so far.... I'm always playing catch up! I've done a lot of the
> grunt work; and I'd like some feedback on what I've done.
>
> Keith
>
>