Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3C4F3D42.2080804@ece.gatech.edu> Date: Wed, 23 Jan 2002 17:46:26 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: keith_starsmeare AT yahoo DOT co DOT uk CC: cygwin-apps AT sources DOT redhat DOT com Subject: Re: setup.exe command line options References: <00b301c1a45e$82614b60$81293c3e AT Obsession> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 AT yahoo DOT co DOT 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 > >