-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 12 December 2002 10:09 am, [EMAIL PROTECTED] wrote: > On Thu, 12 Dec 2002, Praedor Atrebates wrote: > > Failing to find src rpms for KDE 3.0.5 for mandrake, I had to resort to > > Redhat 8.0 src rpms. I can get around the differences without too much > > difficulty except for one brain-dead feature of RPM. A feature that I > > hope I am wrong about and someone will correct me. [...] > > <Rant> > > Building an RPM should NOT be dependent upon noncritical issues like > > documents or other nonintegral froo-froo. Perhaps Mandrake could FIX > > Redhat's broken RPM by making it more fault tolerant so that rpm builds > > can be completed inspite of missing or failing a noncritical portion > > (like doc generation)?! </Rant> > > I dunno if I can agree with that. One thing I like about RPM is that > it makes it easy to reproduce an identical package from the SRC rpm. If > it continued then there's too much room for error when publishing an > RPM.> > > OK, that said, my build attempt died when qt2kdoc was trying to run to > > convert, I believe, qtdocs into kdocs: > > > > qt2kdoc /doc/html > > > > There IS no /doc directory which is what I suspect the problem was. I am > > still unable to find the file that tells the make process to look for qt > > docs in /doc/html but that is besides my point. Is there a way to > > continue an rpm build rather than have to start all over again? It was > > DONE compiling and was simply doing extraneous froo-froo tidying up > > before creating/writing the rpms. If I do an rpm --rebuild or rpm -bb > > kdelibs.spec, I am stuck starting over from scratch from untarring to
Even barring that, the PREBUILD configuration process should catch stuff like this rather than have you build a src package all the way through but have the package creation part at the very end die because of something being not to its liking. It should have caught it at the start! Barring that, then an option to continue despite a boo-boo. So what if docs don't get parsed or converted, the app associated (and the main reason for the package) can still work fine without it. Kdelibs doesn't require html documentation creation in order for the libs to be fully functional to apps. This sort of error is just as bogus as non-opengl apps refusing to run because they cannot find libgl.so.2 or something (when they don't need it in the first place). [...] > > reconfiguring to rebuilding. Is there a way to resume a build? > > You can use the --short-circuit option to start the skip to a different > section of the specfile. I've only used it a couple times and it depends > on what gets cleaned up. I see what I can do. Thanks. praedor -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9+Kj+mkm5RO1gX9cRAnYLAJ9c/RQhUoN9AO34s5H0KSkKTkDAJwCghd4s Uyz9Dn7Ewqt7m+tBPYth2GQ= =2YjQ -----END PGP SIGNATURE-----
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
