Menu
▾
▴
[privoxy-devel] [ ijbswa-Developer TODOs-711668 ] Remove generated docs from CVS
|
From: SourceForge.net <no...@so...> - 2003-03-31 16:20:27
|
Developer TODOs item #711668, was opened at 2003-03-29 03:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=400339&aid=711668&group_id=11118 >Category: None >Group: None >Status: Open Resolution: Fixed Priority: 5 Submitted By: David Mediavilla (davidme) >Assigned to: Nobody/Anonymous (nobody) >Summary: Remove generated docs from CVS Initial Comment: After installing 3.0.2 for OS/2, the documentation PDFs are broken. The files are: 25/08/02 19:41 124.685 0 privoxy-developer-manual.pdf 25/08/02 19:41 124.285 0 privoxy-faq.pdf 25/08/02 19:41 334.316 0 privoxy-user-manual.pdf GSView 4.0 with ChostScript 7.0.3 tells that the error is : Scanning PDF file Unrecoverable error: syntaxerror in readxref Acrobat 3.0 simply says that there is an irrecoverable error. ---------------------------------------------------------------------- >Comment By: Andreas Oesterhelt (oes) Date: 2003-03-31 18:33 Message: Logged In: YES user_id=78811 Very good! Turning into devel-todo. ---------------------------------------------------------------------- Comment By: David Schmidt (david__schmidt) Date: 2003-03-31 17:20 Message: Logged In: YES user_id=249980 OS/2 package with updated .PDFs (that actually work, from the website .zip) has been posted. ---------------------------------------------------------------------- Comment By: David Schmidt (david__schmidt) Date: 2003-03-31 16:36 Message: Logged In: YES user_id=249980 Hal - I think the .PDFs in CVS are bad anyway because they are being stored in text format, and I think they should be binary. I can extract them, but they appear corrupt to both OS/2 and Win32 acrobat readers. Andreas - Yes, OS/2 has tar, so that format is not a problem for packaging. - David ---------------------------------------------------------------------- Comment By: Andreas Oesterhelt (oes) Date: 2003-03-31 16:02 Message: Logged In: YES user_id=78811 I reckon that a tar.gz should work for all Unix-style, cygwin, and Amiga platforms, and David probably has GNU tar on his OS/2 machine, too. Regarding the extra step, all packages that are built via make can do the download automatically. For the others, the build scripts can maybe at least fail if non-optional docs are missing. I'd take no precautions to restrict download to packagers, but wouldn't advertise the URL either. The URL (i.e. the filename) should include the Privoxy version number, so that building the packages fails in the download step if no current archive is available. As soon as the OSX package is up, we can turn this bug into a developer-todo. ---------------------------------------------------------------------- Comment By: David Schmidt (david__schmidt) Date: 2003-03-30 22:53 Message: Logged In: YES user_id=249980 Hal - I'm sure we discussed it, and I'm sure I forgot it. I promise to stick a 'wget' in the OS/2 build script to yank it off the web next time... - David ---------------------------------------------------------------------- Comment By: Hal Burgiss (hal9) Date: 2003-03-30 00:46 Message: Logged In: YES user_id=322640 First, I am committing fresh PDFs to cvs. Sorry David, or anyone that was depending on these. I thought we had had this conversation before and decided to move away from keeping docs in cvs, and in fact, had decided that PDF docs would be kept on the website (and not cvs). But maybe not ;-) OES, your proposal sounds fine to me, but I'd like to hear from some other packagers, and see what is easiest for them. This is essentially adding a step for packagers, which certainly is no big deal. So now we have txt, html, and pdf. Do we want to have a zip archive for each? One big zip file? Should it be public, or just there for packagers? ---------------------------------------------------------------------- Comment By: Andreas Oesterhelt (oes) Date: 2003-03-29 16:34 Message: Logged In: YES user_id=78811 The PDF docs in CVS are very old. Keeping genereated stuff in CVS does suck big time, but there needs to be a way to build packages without jade, docbook & tools available. How about this: Whoever does the release must, after freezing, but before src package upload, update the docs on the webserver, incl. text, pdf, README etc. The package build targets then suck the docs from privoxy.org. We delete generated docs from CVS once and for all. Any objections / ideas? ---------------------------------------------------------------------- Comment By: David Schmidt (david__schmidt) Date: 2003-03-29 14:23 Message: Logged In: YES user_id=249980 Looks like bad .pdfs made it into the OS/2 package. The soonest I can rebuild it is Monday. - David ---------------------------------------------------------------------- Comment By: David Mediavilla (davidme) Date: 2003-03-29 04:50 Message: Logged In: YES user_id=595264 The PDFs from the .zip at privoxy.org work OK. The ones I listed are those present in privoxyos2_setup_3.0.2.exe. So it seems that corrupt files were shipped. ---------------------------------------------------------------------- Comment By: Hal Burgiss (hal9) Date: 2003-03-29 03:57 Message: Logged In: YES user_id=322640 PS -- Those timestamps look like 3.0.0 time frame. Are they accurate? ---------------------------------------------------------------------- Comment By: Hal Burgiss (hal9) Date: 2003-03-29 03:38 Message: Logged In: YES user_id=322640 David, thanks! Unfortunately, I downloaded the 3.0.2 PDF docs from the website, and they are all readable with Acrobat, Ghostview, and xpdf on Linux, with no problems. Soooo....I am guessing we have a corruption problem in the OS/2 packaging process or some other platform specific issue. Can you try the ones posted on http://privoxy.org (assuming you are talking about different ones, of course)? TIA. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=400339&aid=711668&group_id=11118 |