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 Date: Sun, 16 Dec 2001 20:04:08 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: has anyone tried latest setup.exe from cvs ? Message-ID: <20011217010408.GB30991@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <15fe01c1868c$af278230$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15fe01c1868c$af278230$0200a8c0@lifelesswks> User-Agent: Mutt/1.3.23.1i On Mon, Dec 17, 2001 at 10:52:11AM +1100, Robert Collins wrote: > >----- Original Message ----- >From: "Gary R. Van Sickle" >>i.e., that have no "version:" lines in them (what is such an entry >>supposed to mean, or is this actually a upset bug?). The parser then >>never creates a > >Chris, do you consider version: to be mandatory for setup.ini files? > >setup.html doesn't specify (AFAICT) whether version: is optional or >mandatory. If the decision hasn't been made, I'd prefer mandatory. It's optional for setup.exe, certainly. There are a few packages for which there is no version: info. I think I nuked one of them yesterday, though. I don't think that update-setup produced version: lines for packages which had no actual version info, either. I recall having to work around this when I worked on setup.exe. I can't glean enough of what this thread was about from context but I seem to recall that this was actually the problem of entries that had no version, no install, no sources, i.e., the package directories were empty. That was my screwup, since rectified. upset is rather weak on complaining about things like that but it should do so eventually. I'll make it issue a warning and skip the directly entirely. cgf