From: "John M. Aldrich" Newsgroups: comp.os.msdos.djgpp Subject: DJVERIFY (Was: Re: GCC question) Date: Mon, 28 Jul 1997 20:48:25 +0000 Organization: Two pounds of chaos and a pinch of salt Lines: 42 Message-ID: <33DD0599.42E7@cs.com> References: <19970728213301 DOT RAA24433 AT ladder01 DOT news DOT aol DOT com> <5rjalf$ocf AT news DOT ox DOT ac DOT uk> Reply-To: fighteer AT cs DOT com NNTP-Posting-Host: ppp107.cs.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk George Foot wrote: > > You might consider getting DJVERIFY. This utility is not complete, but it > is intended to check that people have installed djgpp properly. I'm not > sure where you can get it from; I think perhaps FTP from ftp.delorie.com, > in an alpha directory maybe? I think the filename is vrfy033a.zip or > something similar. It can produce a full, detailed report of your > configuration which you can post here. And, believe it or not, I've started working on DJVERIFY again. The major hassle has been keeping up with all the GNU package updates for my tracking system. This brand-new part of DJVERIFY 0.4 will detect what packages you have installed on your system and will allow you to look up any file in a package by name. Of course, to build it, I need at least the manifests from every zipfile, and I need the zipfiles themselves if I want the program to be able to calculate the installed size of the packages (another planned feature for the next version). This means a lot of downloading, and a lot of disk space. :) Finally, I'm working on updating the interface. Shouldn't be too long now, folks. BTW, I have two questions to ask: one general, one specific. First, would it pain people too much if I didn't include the new TeX distribution files in at least the initial release of DJVERIFY 0.4? Those suckers are big; I don't want to mess with them unless there is a provable demand. Second, once a stable release of DJVERIFY is available, what would be the most reliable method to distribute new package data files so that new users can get the latest available information but old users can update their information without needing to redownload the entire program? I was thinking of maintenance uploads every time a new package comes out, indexed by date and also posted on my web site, but I will defer to the wisdom of anyone with more experience in these matters. Thanks for your patience! -- --------------------------------------------------------------------- | John M. Aldrich | "It may be better to be a live jackal| | aka Fighteer I | than a dead lion, but it is better | | mailto:fighteer AT cs DOT com | still to be a live lion." | | http://www.cs.com/fighteer | - Lazarus Long | ---------------------------------------------------------------------