> Looks like you figured out upset. Sorry about not responding. Actually, I did the same thing that Ian did and reverted to the upset from: [EMAIL PROTECTED]:/cvs/src
in the directory: winsup/cinstall/temp That version of upset reports the version number as the whole file name before the .tar.bz2 (i.e. XFree86-bin-4.2.0-1 instead of 4.2.0-1) and also manages to mangle the version reported from setup.exe: setup-version: 2.194.2.24^@ %d.%d.%d.%d^@Can't Oh well, at least I got the script to do a little bit of what I needed it for. :) > It needs at least an empty tar file. Okay. I'm working on that now. > >2) I'm not sure why, but uninstalling packages often leaves files > >around. For example, uninstalling XFree86-f100 delete all files from > >/usr/X11R6/lib/X11/fonts/100dpi/ except for "UTRG__24.pcf.gz". Weird. > > There was another report of cygwin not removing files in the cygwin > mailing list. Was that possibly the last in the list from a > /etc/setup/whatever.lst.gz file? Yes. That is it exactly. I also tried this with the XFree86-bin file and it failed to remove libXxf86vm.a, which was the last file in XFree86-bin.lst.gz. > >3) We may need a short post-install script, based off of Xinstall.sh, > >that runs mkfontdir in the /usr/X11R6/lib/X11/fonts/local and > >/usr/X11R6/lib/X11/fonts/misc font directories. Xinstall.sh says it > >does this to make sure that these directories are "up to date". I > >guess that every font package has the right to install fonts in local > >or misc, but it seems that none of them do. Perhaps this won't matter. > > How about mounting the font directory in binmode, too? Excellent idea. Now I just need someone to write that script. Shouldn't be too hard. Any takers? Harold