Please upload: doxygen v1.4.2-20050410

[Max Bowsher]

My message that I quote here, was accidentally sent privately - sorry, that 
was a mistake.

Max Bowsher wrote:
> Hans W. Horn wrote:
>> Please upload the latest doxygen release for cygwin (v1.4.2-20050410)
>>
>> Binaries, sources & setup.hint files are located at
>> http://www.geocities.com/hannes_horn/cygwin/doxygen/
>>
>> -rw-rw-rw-  1 hanshorn Power Users 1823811  Apr 11 23:44
>> doxygen-1.4.2-20050410-src.tar.bz2
>> -rw-rw-rw-  1 hanshorn Power Users 1474000  Apr 11 23:43
>> doxygen-1.4.2-20050410.tar.bz2
>> -rwx------+   1 hanshorn Power Users         351  Apr 11 08:26 setup.hint
>>
>> Since yahoo free webhosting doesn't allow files with the .bz2 extension, 
>> I
>> changed the extension of the package files to tgz. Just save these files
>> back as .bz2.
>
> Eeek. Nasty.
>
>> Same with setup.hint. Here I simply appended .html; just save without
>> .html.
>
> Also nasty. Is it possible you could continue looking for a less obnoxious
> webhost?

This point stands, but...

>> Since this is my first contribution of this kind, please bear with me if 
>> I
>> didn't get it all right off the bat.
>
> Do you suppose you could follow the package format described at "Method 
> Two"
> on http://cygwin.com/setup.html, rather than inventing your own script?

I retract this suggestion. Having had a closer look at the doxygen 
buildsystem, it would require sufficient adaptations to the generic build 
script, that it is not worth it.

> I think preserving the original distibution's tarball untouched is a good
> thing to do.

Although this is still a nice thing to do - bundle the source tarball, with 
a patch file, and a script which unpacks the source and applies the patch. 
This means that people looking at your package in the future can tell 
exactly what changes needed to be made for the Cygwin package, without 
needing to fetch the upstream tarball seperately and comparing them.

Max.