Brian Dessent wrote on Monday, May 05, 2008 4:12 PM: > And again, to recap: the reason for generating an error instead of > silently moving on in this situation was to diagnose the case where > the maintainer used a strange tar implementation to create a package > -- without the error the package will be silently skipped which is > very confusing. But it seems like this nonsense 10k of zeros will > have to be special cased in order to be able to detect the desired > error case from the bogus error case. > > In the mean time, I suggest you use a real empty file as workaround > (i.e. bzip2 </dev/null >file.tar.bz2) as that should correctly be > detected as an empty package if you're using the current setup.
Thanks for the explanation. I used 'bzip2 < /dev/null > file.tar.bz2', generating a 14 byte tar.bz2 file, and setup.exe handles it just fine. -- Bryan Thrall FlightSafety International [EMAIL PROTECTED]