Re: [PACKAGE UPDATE] ccdoc-0-8.41-2
I am happy to. To avoid my cygwin-apps fiasco I need your help. Should the announcement look something like this? Subject: Updated: ccdoc-0.8.41 An updated version of ccdoc has been released with a number of bug fixes. For more details about the release see http://ccdoc.sourceforge.net. It is my understanding that one of the moderators will then inspect this message and prepend [ANNOUNCEMENT] to the subject. Cheers, Joe Christopher Faylor wrote: On Fri, Oct 08, 2004 at 10:24:54AM +0200, Corinna Vinschen wrote: On Oct 7 08:02, Joe Linoff wrote: Corinna Vinschen wrote: On Oct 6 19:38, Joe Linoff wrote: http://ccdoc.sourceforge.net/cygwin/ccdoc-0.8.41-2.tar.bz2 http://ccdoc.sourceforge.net/cygwin/ccdoc-0.8.41-2-src.tar.bz2 http://ccdoc.sourceforge.net/cygwin/setup.hint Uploaded. Did replace mean I should remove 0.8.39-1? Usually it's no bad idea to keep one older version for a while... Yes, I meant to replace 0.8.39-1 with 0.8.41-2. Ok, removed. Are you going to send an announcement to cygwin-announce, btw? Yes, please. I think this was missing from the last time ccdoc was released. cgf -- This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Re: [PACKAGE UPDATE] ccdoc-0-8.41-2
Corinna Vinschen wrote: On Oct 6 19:38, Joe Linoff wrote: Please upload the following to replace ccdoc-0.8.39-1: http://ccdoc.sourceforge.net/cygwin/ccdoc-0.8.41-2.tar.bz2 http://ccdoc.sourceforge.net/cygwin/ccdoc-0.8.41-2-src.tar.bz2 http://ccdoc.sourceforge.net/cygwin/setup.hint Uploaded. Did replace mean I should remove 0.8.39-1? Usually it's no bad idea to keep one older version for a while... Yes, I meant to replace 0.8.39-1 with 0.8.41-2. Cheers, Joe Thanks, Corinna -- This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
update - ccdoc 08.41 is ready for experimentation
ccdoc 08.41 is ready for experimentation The distribution can be uploaded from: http://ccdoc.sourceforge.net/cygwin/ccdoc-08.41-1-src.tar.bz2 http://ccdoc.sourceforge.net/cygwin/ccdoc-08.41-1.tar.bz2 http://ccdoc.sourceforge.net/cygwin/setup.hint Thanks.
Re: update - ccdoc 08.41 is ready for experimentation
I am afraid that I am not sure what you mean by beta-test but I don't think that the program needs to be tested at all. This version of ccdoc has been released to sourceforge and is already in the public domain. The reason I submitted it to this group for approval was because I was bit confused by the cygwin submission documentation and wasn't sure whether I got the directory structures right in the tar files. Here is the directory structure for the binary release (ccdoc-08.41-1.tar.bz2): usr/ usr/bin/ usr/bin/ccdoc.exe usr/share/ usr/share/doc/ usr/share/doc/ccdoc-08.41-1/ usr/share/doc/ccdoc-08.41-1/LICENSE usr/share/doc/ccdoc-08.41-1/README usr/share/doc/ccdoc-08.41-1/RELEASE_NOTES usr/share/doc/Cygwin/ usr/share/doc/Cygwin/ccdoc-08.41-1.README usr/share/man/ usr/share/man/man1/ usr/share/man/man1/ccdoc.1 I apologize in advance if this was not the correct forum for this type of verification. If that is the case, can you point me in the right direction? Christopher Faylor wrote: On Wed, Oct 06, 2004 at 02:40:32PM -0700, Joe Linoff wrote: ccdoc 08.41 is ready for experimentation The distribution can be uploaded from: http://ccdoc.sourceforge.net/cygwin/ccdoc-08.41-1-src.tar.bz2 http://ccdoc.sourceforge.net/cygwin/ccdoc-08.41-1.tar.bz2 http://ccdoc.sourceforge.net/cygwin/setup.hint This isn't a beta testing list. Are you saying that this is ready for upload to the main cygwin site? -- This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Re: update - ccdoc 08.41 is ready for experimentation
I am afraid that I am not sure what you mean by beta-test but I don't think that the program needs to be tested at all. This version of ccdoc has been released to sourceforge and is already in the public domain. The reason I submitted it to this group for approval was because I was bit confused by the cygwin submission documentation and wasn't sure whether I got the directory structures right in the tar files. Here is the directory structure for the binary release (ccdoc-08.41-1.tar.bz2): usr/ usr/bin/ usr/bin/ccdoc.exe usr/share/ usr/share/doc/ usr/share/doc/ccdoc-08.41-1/ usr/share/doc/ccdoc-08.41-1/LICENSE usr/share/doc/ccdoc-08.41-1/README usr/share/doc/ccdoc-08.41-1/RELEASE_NOTES usr/share/doc/Cygwin/ usr/share/doc/Cygwin/ccdoc-08.41-1.README usr/share/man/ usr/share/man/man1/ usr/share/man/man1/ccdoc.1 I apologize in advance if this was not the correct forum for this type of verification. If that is the case, can you point me in the right direction? Christopher Faylor wrote: On Wed, Oct 06, 2004 at 02:40:32PM -0700, Joe Linoff wrote: ccdoc 08.41 is ready for experimentation The distribution can be uploaded from: http://ccdoc.sourceforge.net/cygwin/ccdoc-08.41-1-src.tar.bz2 http://ccdoc.sourceforge.net/cygwin/ccdoc-08.41-1.tar.bz2 http://ccdoc.sourceforge.net/cygwin/setup.hint This isn't a beta testing list. Are you saying that this is ready for upload to the main cygwin site? -- This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Re: update - ccdoc 08.41 is ready for experimentation
Should I re-submit this with the ITP designation? Reini Urban wrote: Joe Linoff schrieb: I am afraid that I am not sure what you mean by beta-test but I don't think that the program needs to be tested at all. This version of ccdoc has been released to sourceforge and is already in the public domain. The reason I submitted it to this group for approval was because I was bit confused by the cygwin submission documentation and wasn't sure whether I got the directory structures right in the tar files. Here is the directory structure for the binary release (ccdoc-08.41-1.tar.bz2): usr/ usr/bin/ usr/bin/ccdoc.exe usr/share/ usr/share/doc/ usr/share/doc/ccdoc-08.41-1/ usr/share/doc/ccdoc-08.41-1/LICENSE usr/share/doc/ccdoc-08.41-1/README usr/share/doc/ccdoc-08.41-1/RELEASE_NOTES usr/share/doc/Cygwin/ usr/share/doc/Cygwin/ccdoc-08.41-1.README usr/share/man/ usr/share/man/man1/ usr/share/man/man1/ccdoc.1 I apologize in advance if this was not the correct forum for this type of verification. If that is the case, can you point me in the right direction? packaging looks perfect to me, just your wording was irritating. You need a subject like: [ITP] ccdoc 08.41 And then a sentence in which you state that you want to maintain this cygwin package. The reviewers will point to problems in your packaging or licensing. upload is reserved for packages which already got their 3 positive reviews and one GTG (good to go). Christopher Faylor wrote: On Wed, Oct 06, 2004 at 02:40:32PM -0700, Joe Linoff wrote: ccdoc 08.41 is ready for experimentation The distribution can be uploaded from: http://ccdoc.sourceforge.net/cygwin/ccdoc-08.41-1-src.tar.bz2 http://ccdoc.sourceforge.net/cygwin/ccdoc-08.41-1.tar.bz2 http://ccdoc.sourceforge.net/cygwin/setup.hint This isn't a beta testing list. Are you saying that this is ready for upload to the main cygwin site? -- This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Re: update - ccdoc 08.41 is ready for experimentation
Reini Urban wrote: Reini Urban schrieb: You need a subject like: [ITP] ccdoc 08.41 Why this funny version number? It should be called ccdoc-0.8.41 imho. Or if MAJOR is 8 leave the 0 away = ccdoc-8.41 This is irritating. Thanks for the insight. I would strongly prefer ccdoc-0.8.41 but the cygwin documentation seemed to state that it required two numbers. Since it sounds like it is allowed, I will change it to 0.8.41 and re-submit it tomorrow. BTW: This is the longest -h message I've ever seen. Was the intent to make ccdoc -h be longer then man ccdoc :) Just joking. I just love typing... And then a sentence in which you state that you want to maintain this cygwin package. The reviewers will point to problems in your packaging or licensing. upload is reserved for packages which already got their 3 positive reviews and one GTG (good to go). err, update, you know what I mean. ok, to the review: binary package looks fine. src package has /usr/src/ccdoc-08.41-1.patch hardcoded, which may not be! even if it's empty. The rest is simple, but okay. I like this much better and will do it tomorrow. I don't like hardcoded paths in tarfiles. It might be helpful to update the http://cygwin.com/setup.html because it seemed to indicate that the preferred method is to hard code the patch to /usr/src/foo-vendor-release.patch. See paragraph 4 (or so) in the Method One subsection under the Package Source section. Please just remove the patch file from this path. You might want to add this empty ccdoc-08.41-1.patch to topdir. but then you have to call tar cfj differently. Okay. I will add the patch to ccdoc-0.8.41-#/CYGWIN-PATCHES/ccdoc-0.8.41-#.patch where # is either 1 or 2 depending on whether the name change from ccdoc-08.41 to ccdoc-0.8.41 affects things. With these fixes +1 and GTG. It sounds like the new release should be ccdoc-0.8.42-2 even though the name changed. Thanks for taking the time to review this. I will make the changes and re-submit it tomorrow with the ITP designation. At least I have now a full cygwin class documentation: $ cd /usr/src $ ccdoc -db /tmp/ccdoc.db -pkg Cygwin src/winsup/cygwin/*.h $ ccdoc -db /tmp/ccdoc.db -index $ mkdir -p cygwin-ccdocs/images # required $ ccdoc -db /tmp/ccdoc.db -html cygwin-ccdocs/ -imgurl images/ -root winsup -rooturl winsup.html Wow, you are a quick study...
Re: update - ccdoc 08.41 is ready for experimentation
Christopher Faylor wrote: On Wed, Oct 06, 2004 at 04:06:21PM -0700, Joe Linoff wrote: I am afraid that I am not sure what you mean by beta-test but I don't think that the program needs to be tested at all. Any reason for sending this multiple times? What everyone seems to be missing is this: http://cygwin.com/cgi-bin2/package-cat.cgi?file=ccdoc%2Fccdoc-0.8.39-1grep=ccdoc ccdoc is already part of the distribution. That's what I mean by beta test. I don't understand why you'd send a ready for experimentation message here. Do you see any other messages like that in this mailing list? No, but the setup.html specifically refers to experimentation in step 9 of the submitting a package guidelines. This version of ccdoc has been released to sourceforge and is already in the public domain. The reason I submitted it to this group for approval was because I was bit confused by the cygwin submission documentation and wasn't sure whether I got the directory structures right in the tar files. Here is the directory structure for the binary release (ccdoc-08.41-1.tar.bz2): Why are you having problems figuring out how to package this after having already provided it once before: http://sources.redhat.com/ml/cygwin-apps/2003-02/msg00270.html I'm thoroughly confused. You are the package maintainer but you, and everyone else are treating this like a new experience. It is a new experience, sort of. This time I tried to the follow the http:://cygwin.com/setup.html instructions as closely as possible. In doing so, I ran across a number of things that appeared different than last time: 1. Version number appeared to be major.minor. 2. The patch file was supposed to be hard coded to /usr/src/foo-vendor-release.patch. 3. Binary release files went to /usr/share/man and /usr/share/doc. I think that is where I got into trouble. Cheers, Joe cgf -- This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
[PACKAGE UPDATE] ccdoc-0-8.41-2
Hi: Please upload the following to replace ccdoc-0.8.39-1: http://ccdoc.sourceforge.net/cygwin/ccdoc-0.8.41-2.tar.bz2 http://ccdoc.sourceforge.net/cygwin/ccdoc-0.8.41-2-src.tar.bz2 http://ccdoc.sourceforge.net/cygwin/setup.hint There are no cygwin related changes. Thanks, Joe
Re: update - ccdoc 08.41 is ready for experimentation
Christopher Faylor wrote: On Wed, Oct 06, 2004 at 07:33:50PM -0700, Joe Linoff wrote: Christopher Faylor wrote: On Wed, Oct 06, 2004 at 04:06:21PM -0700, Joe Linoff wrote: I am afraid that I am not sure what you mean by beta-test but I don't think that the program needs to be tested at all. Any reason for sending this multiple times? What everyone seems to be missing is this: http://cygwin.com/cgi-bin2/package-cat.cgi?file=ccdoc%2Fccdoc-0.8.39-1grep=ccdoc ccdoc is already part of the distribution. That's what I mean by beta test. I don't understand why you'd send a ready for experimentation message here. Do you see any other messages like that in this mailing list? No, but the setup.html specifically refers to experimentation in step 9 of the submitting a package guidelines. That was a poor choice of words (it was probably mine) but it wasn't referring to cygwin-apps, anyway. I'm thoroughly confused. You are the package maintainer but you, and everyone else are treating this like a new experience. It is a new experience, sort of. This time I tried to the follow the http:://cygwin.com/setup.html instructions as closely as possible. In doing so, I ran across a number of things that appeared different than last time: 1. Version number appeared to be major.minor. The page says: Package naming scheme: use the vendor's version plus a release suffix for ports of existing packages... No one is forcing you to do make it major.minor. There are a number of examples of packages which are more than just major.minor but a really obvious one is the cygwin DLL itself. I can see that now. 2. The patch file was supposed to be hard coded to /usr/src/foo-vendor-release.patch. There are two patch methods and I don't believe that they have changed substantially in years. I am sure that you are right. I saw the two different patch methods but I thought that the documentation said that the preferred method was to that this file should extract as: /usr/src/ I interpreted that to mean a hard-coded reference in the tarfile. When I re-submitted this request as an update, I changed the patch so that it used the old method. 3. Binary release files went to /usr/share/man and /usr/share/doc. I think that is where I got into trouble. It sounds like where you really got into trouble was not following the discussion about packages that has gone on since you last submitted ccdoc. As a package maintainer, you should be subscribed to cygwin-apps and you should be at least monitoring discussions about changes to package conventions (like moving from /usr/man to /usr/share/man). None of this should be a surprise. You are correct. I will be more vigilant in the future. Thanks for pointing this out. cgf -- This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Re: Request #2 to add a new package: ccdoc
Hi Pavel: Thanks for taking the time to detail the issues. It really helps novices like me: Pavel Tsekov wrote: I've made a brief review of the packaging, but not the functionality. Here is a list of problems that need to be fixed: 1) The source package includes files/dirs left by tools like autoconf and configure. These need to be removed. I see there is no 'distclean' stage in you Makefile, so I guess the right place is in 'clean'. I fixed this and added a distclean target. 2) Some of the files in the source package contain unix line endings, while others have dos line endings. All files should have unix line endings. All sources files have unix line endings now. 3) The excutable file in the binary package should be stripped by running 'strip executable_file'. The strip program is now run as part of the link target. 4) The man page in the binary pakage has a name of 'ccdoc.man'. Should be ccdoc.1. Seems like something is wrong with the 'install-man' stage in your Makefile. The ccdoc.man name was changed to ccdoc.1 The install_man stage was fixed. It turned out to be a configure script problem (default was /usr/local rather than /usr). 5) The source package should contain a dir called CYGWIN-PATCHES. This dir contains Cygwin specific files - like Cygwin specific README, setup.hint and other files. In the case of ccdoc it should contain setup.hint. Then you should generate a patch. To see how to generate this patch and what is its purpose visit the following link: http://cygwin.com/setup.html#srcpackage_contents This CYGWIN-PATCHES subdirectory has been added. The ccdoc-0.8.39-1.patch file has been added. Thanks! You can find the updated package distribution files here: http://ccdoc.sourceforge.net/cygwin_tmp/ccdoc-0.8.39-1 Cheers, Joe
Re: Request to add a new package: ccdoc
I like that even better. I will re-submit this request today with this version number. Thank you for your patience. Joe Pavel Tsekov wrote: On Wed, 26 Feb 2003, Joe Linoff wrote: Ccdoc has been using that convention (A.B.C-D) for last 3 years or so. The current version 0.8 and the release is 39 so I thought that ccdoc-0.8-39 was correct. Unfortunately, as you pointed out, the 39 designation is NOT correct because ccdoc has NOT been in cygwin. I will change it to ccdoc-0.8-1 as you suggested. What about ccdoc-0.8.39-1 ?
Request #2 to add a new package: ccdoc
Hi Folks: I have fixed the version number with Pavel's help. I have a package that I would like to add to cygwin. setup.hint @ ccdoc category: Dev requires: cygwin version: 0.8.39-1 sdesc: "Generates HTML documentation for C++ interfaces." ldesc: "Automatically generates HTML web documentation from C++ programs by parsing the source file headers. It was designed to aid collaboration between package users and package developers by documenting the interface. More information about ccdoc can be found on the project page: http://ccdoc.sourceforge.net " Here is a URL that will allow you to access the proposed package files: http://ccdoc.sourceforge.net/cygwin_tmp/ccdoc-0.8.39-1 There are three files: setup.hint ccdoc-0.8.39-1-src.tar.bz2 ccdoc-0.8.39-1.tar.bz2 Cheers, Joe
Request to add a new package: ccdoc
Hi Folks: I have a package that I would like to add to cygwin. setup.hint @ ccdoc category: Dev requires: cygwin version: 0.8-39 sdesc: Generates HTML documentation for C++ interfaces. ldesc: Automatically generates HTML web documentation from C++ programs by parsing the source file headers. It was designed to aid collaboration between package users and package developers by documenting the interface. More information can be found on the project page: http://ccdoc.sourceforge.net; Here is a URL that will allow you to access the proposed package files: http://ccdoc.sourceforge.net/cygwin/ Cheers, Joe
