Please upload: doxygen v1.4.2-20050410
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. Same with setup.hint. Here I simply appended .html; just save without .html. Since this is my first contribution of this kind, please bear with me if I didn't get it all right off the bat. Hans
Re: Please upload: doxygen v1.4.2-20050410
Hans W. Horn wrote: Since this is my first contribution of this kind, please bear with me if I didn't get it all right off the bat. Thanks again for offering to maintain this. A couple of notes though: The binaries in your package are still in /usr/local/bin. They need to go in /usr/bin. Also, you included a manpage for doxywizard but there's no binary for it. It's also customary to include a Cygwin-specific README that unpacks into /usr/share/doc/Cygwin/package-x.y-z.README that contains basic notes about the port, who the maintainer is, and where the upstream homepage is. You didn't include any of the html documentation as the previous package did. That's of course your choice as maintainer but I find that the manpage is really pretty lacking, it hardly says anything at all. Brian
Re: Please upload: doxygen v1.4.2-20050410
Brian Dessent wrote: Thanks again for offering to maintain this. A couple of notes though: Oh, and you should strip all the .exe files as well. That shaves off about 1.5MB. Brian
Re: Please upload: doxygen v1.4.2-20050410
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.
Re: doxygen status
Chris, btw. quoting http://cygwin.com/setup.html: Submitting a package ... 7. So you've got a package you want to submit. Follow the following checklist before emailing cygwin-apps@cygwin.com and you'll almost certainly save time. Announce on cygwin-apps@cygwin.com that you have the package ready for uploading. Add the URLs to all package files to your mail or, if you can't provide it on a web page, someone with upload privileges will contact you to get access to the package files to upload them to sourceware.org for you. If the above is not true, then it should be corrected, shouldn't it? H. Christopher Faylor wrote: On Mon, Apr 11, 2005 at 10:30:43AM -0700, Hans W. Horn wrote: I've packaged tested the latest doxygen release (1.4.2-20050410) after applying Max' latest patch (http://bugzilla.gnome.org/show_bug.cgi?id=300204). Since this is my first package contribution: how do I go about uploading? I currently don't have a webserver where I can stage the packages. That's rather a show stopper. We usually use the pull model for retrieving packages, which means you need to have a web site. Can't you use one of the free web hosting facilities? cgf
Re: doxygen status
On Tue, Apr 12, 2005 at 01:39:12PM -0700, Hans W. Horn wrote: Chris, btw. quoting http://cygwin.com/setup.html: Submitting a package ... 7. So you've got a package you want to submit. Follow the following checklist before emailing cygwin-apps@cygwin.com and you'll almost certainly save time. Announce on cygwin-apps@cygwin.com that you have the package ready for uploading. Add the URLs to all package files to your mail or, if you can't provide it on a web page, someone with upload privileges will contact you to get access to the package files to upload them to sourceware.org for you. If the above is not true, then it should be corrected, shouldn't it? I changed the documentation. cgf
Re: doxygen status
On Tue, 12 Apr 2005, Christopher Faylor wrote: On Tue, Apr 12, 2005 at 01:39:12PM -0700, Hans W. Horn wrote: Chris, btw. quoting http://cygwin.com/setup.html: Submitting a package ... 7. So you've got a package you want to submit. Follow the following checklist before emailing cygwin-apps@cygwin.com and you'll almost certainly save time. Announce on cygwin-apps@cygwin.com that you have the package ready for uploading. Add the URLs to all package files to your mail or, if you can't provide it on a web page, someone with upload privileges will contact you to get access to the package files to upload them to sourceware.org for you. If the above is not true, then it should be corrected, shouldn't it? I changed the documentation. FWIW, items 6 and 7 now contradict, and should probably be merged into one item... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
Re: doxygen status
Chris, Christopher Faylor wrote: ...We usually use the pull model for retrieving packages, which means you need to have a web site. Can't you use one of the free web hosting facilities? I already went through two free hosting providers. The first one I tried (netfirms) had a limit of 256k on downloads and wouldn't provide directory listings. The second one I tried (Yahoo / geocities) does not allow bz2 and .hint files to be stored. Max finds it nasty just to rename extensions. Which free ones do the experts recommend? H.
Re: Please upload: doxygen v1.4.2-20050410
Hi Brian Max, Brian Dessent wrote: The binaries in your package are still in /usr/local/bin. They need to go in /usr/bin. In http://cygwin.com/ml/cygwin-apps/2005-03/msg00067.html, you only mentioned the manpages that would need to be in a new home. Will fix. Also, you included a manpage for doxywizard but there's no binary for it. Will fix. It's also customary to include a Cygwin-specific README that unpacks into /usr/share/doc/Cygwin/package-x.y-z.README that contains basic notes about the port, who the maintainer is, and where the upstream homepage is. Will add. You didn't include any of the html documentation as the previous package did. That's of course your choice as maintainer but I find that the manpage is really pretty lacking, it hardly says anything at all. What an oversight of mine. Will add. Max Bowscher wrote: I think preserving the original distibution's tarball untouched is a good thing to do. In the next round I'll provide the original sources + patch, rather than the patched sources. I have pulled http://www.geocities.com/hannes_horn/cygwin/doxygen/. A new announcement is forthcoming. H.
Re: Please upload: doxygen v1.4.2-20050410
Hans W. Horn wrote: The binaries in your package are still in /usr/local/bin. They need to go in /usr/bin. In http://cygwin.com/ml/cygwin-apps/2005-03/msg00067.html, you only mentioned the manpages that would need to be in a new home. Will fix. Sorry for the misunderstanding, I was only referring to the docs there. The current package has binaries in /usr/bin which is the correct place, which is why I didn't mention them. There should never be anything under /usr/local in any package. Brian
Please upload: doxygen v1.4.2-20050410 (2nd take)
Please upload the latest doxygen release for cygwin (v1.4.2-20050410) Binaries, sources setup.hint files are located at http://www.smithii.com/files/cygwin/hans/ (thanks to Ross Smith II for providing web space). -rw-r--r-- 1 32237 ross 2558933 Apr 12 20:18 doxygen-1.4.2-20050410.tar.bz2 -rw-r--r-- 1 32237 ross 1824834 Apr 12 20:19 doxygen-1.4.2-20050410_src.tar.bz2 -rw-r--r-- 1 32237 ross 179 Apr 12 20:22 md5.sum -rw-r--r-- 1 32237 ross 351 Apr 12 20:19 setup.hint Since this is the 2nd attempt of my first contribution of this kind, please bear with me if I still didn't get it all right. I honored various complaints by Brian Dessent and Max Bowscher. Hans
