From: "Ulf Lamping"
| >1) When I downloaded the source (with Mozilla), the name it gave on
my
| >computer was "ethereal-0.10.0a.tar.gz.tar". I didn't have a utility
to
| >unpack that, so I went down the hall to another programmer who
managed
| >to unpack it with a tool he had. He had to rename it to
| >"ethereal-0.10.0a.tar.gz" for his tool to work.
| >
| That Mozilla appended another .tar to the filename is a bug I
| experienced at other places too.
| I'm not sure if this is a Mozilla issue, or a problem with the MIME
| settings on the server.
|
| See 3) for the tool question.
Don't worry: this seems to happen with MSIE too, but the file is then
named .tar.tar.
| >Windows users expect .zip files, but if that is too much of a
| >maintenance problem, it would be nice if there were a link on your
site
| >to a tar tool and explicit instructions how to use it.
| >
| Well, unix users expect .tar.gz files for source code, again see 3)
for
| tools.
|
| >3) Could you zip up the necessary extra tools needed for MSVC users
| >(that is, sed, flex, bison, python, perl) so that I don't have to
chase
| >them down?
| >
| I don't know, if it would be enough to have simply the binary files
| (.exe) available in one dir,
| or if many of additional files had to be added. We also might have
to
| include the source for the tools too?
| It's worth a try nonetheless.
|
| We could use the tools from the cygwin packages, and put them in a
| win32tools.zip (or msvctools.zip?).
| Which should be put in the rootdir.
Umm... cygwin registers some vital things into the Windows registry.
What we may want to do, is provide a minimal set of cygwin packages as
a fake cygwin repository on the Ethereal webserver. This way, the
end-user would use the cygwin setup tool, and only retrieve packages
from the limited Ethereal development cygwin mirror.
Regards,
Olivier