Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))
On Apr 25 14:09, Christopher Faylor wrote: On Sat, Apr 23, 2005 at 12:35:19AM +0100, Max Bowsher wrote: Accordingly, I hereby ITP doxygen myself: I've waited several days to respond to this because I wanted to make sure that I was in the proper emotional state and didn't just fire off a knee-jerk reaction. Nevertheless, I remain appalled by this turn of events. I saw nothing in Hans' email which indicated that he's unwilling to be cooperative about packaging problems so I see no reason to pull the package from him. Hans is not the first person to have to go through a moderate amount of pain before getting the packaging right and if the biggest complaint of his source packaging is that it doesn't contain the cygwin README, then that is not a big deal. I don't know how to resolve this situation but I do know for sure that neither Corinna nor I are going to reward someone by making them a package maintainer after essentially publicly insulting another volunteer. Hans, this is still yours if you want it. Otherwise, MaxB has disqualified himself from doxygen package maintainership, so I guess we're in the market for a maintainer again. Hans' binary package looks ok to me. The source package might have some minor problems but I'd be dead surprised if not any of my packages would have problems either. I don't quite understand all that hype around the source packages anyway. The source package provides the sources which have been used to build the binary package. That's all, no need to create a science from it. A minor problem in the source file is certainly no reason to kick somebody's a**. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc.
Re: ITP: cramfs-1.1, mtd-20050419
On Apr 25 16:18, Robb, Sam wrote: One concern: the mtd source package is rather large, as it is a snapshot of the whole mtd source tree. If this is a concern, I can work on trimming down the sources to just the essentials needed to build the utilities. What's rather large in MB? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc.
Please upload: ELFIO-1.0.2-1
Hi All, Please upload a new ELFIO-1.0.2 package available at: http://elfio.sourceforge.net/ELFIO-1.0.2-1.tar.bz2 http://elfio.sourceforge.net/ELFIO-1.0.2-1-src.tar.bz2 http://elfio.sourceforge.net/setup.hint Release focus: Update to version 1.0.2 Thank you, Serge _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))
Chris, Corinna Max, thanks but no thanks. I had a real rough start with this, which utterly discouraged me and dampened my enthusiasm to maintain anything at this time considerably! So please consider doxygen and bash to be up again for grabs! As far as I am concerned, can't you just let Max be doxygen maintainer if he still wants to? The least I want is to seed trouble among the cygwin core team and long-time maintainers such as Max. H. Christopher Faylor wrote: On Sat, Apr 23, 2005 at 12:35:19AM +0100, Max Bowsher wrote: Hans W. Horn wrote: Alright, Max Bowsher wrote: No, still wrong. You didn't read what I said carefully enough. You *need* to understand: Filenames are expected to be EXACTLY: NAME-VERSION-RELEASE.tar.bz2 NAME-VERSION-RELEASE-src.tar.bz2 I guess I never appreciated the subtle naming convention used for cygwin packages. Honestly, my impression was that names go all over the map. Fixed (I think). +++ doxygen_1.4.2-20050410/doc/language.doc +++ doxygen_1.4.2-20050410/doc/translator_report.txt +++ doxygen_1.4.2-20050410/examples/example.tag These files are touched during a 'make install_docs'. Excluded offending diffs from patch. Having got the superficial naming problems out of the way, I took a closer look at the source packaging. There were many issues - the most serious being that the source package did not even contain the Cygwin specific readme at all - and many minor deficiencies related to using a home-grown build script, rather than the tried-and-true cygwin template. I am sorry, but the conclusion I came to was that it would be less effort for me to produce my own packages of doxygen, based on the the generic-build-script, than to assist in getting these packages up to a good-to-go status. Accordingly, I hereby ITP doxygen myself: Setup.exe installation site: http://unicorn.robinson.cam.ac.uk/~mob22/cygdoxygen/ I've waited several days to respond to this because I wanted to make sure that I was in the proper emotional state and didn't just fire off a knee-jerk reaction. Nevertheless, I remain appalled by this turn of events. I saw nothing in Hans' email which indicated that he's unwilling to be cooperative about packaging problems so I see no reason to pull the package from him. Hans is not the first person to have to go through a moderate amount of pain before getting the packaging right and if the biggest complaint of his source packaging is that it doesn't contain the cygwin README, then that is not a big deal. I don't know how to resolve this situation but I do know for sure that neither Corinna nor I are going to reward someone by making them a package maintainer after essentially publicly insulting another volunteer. Hans, this is still yours if you want it. Otherwise, MaxB has disqualified himself from doxygen package maintainership, so I guess we're in the market for a maintainer again. cgf
Re: ITP: cramfs-1.1, mtd-20050419
On Apr 25 16:18, Robb, Sam wrote: One concern: the mtd source package is rather large, as it is a snapshot of the whole mtd source tree. If this is a concern, I can work on trimming down the sources to just the essentials needed to build the utilities. What's rather large in MB? The mtd source package is currently 1.3 MB compressed. A quick cut that removes obviously unused/unreferenced top-level directories trims that down to about 350 K. I could probably trim it back to around 250 K by eliminating some unused sub- directories (ecos support, test harnesses, etc.) -Samrobb
