Quality Guides up to date!

[Carlos Leonhard Woelz]

On Mon, 23 May 2005 19:12:40 -0400, "Michael Pyne"
<pynm0001 at comcast.net> said:
> Just a note about kdesvn-build.  Its intent is certainly to "build
> everything" 
> for you.  However, you can use it to build only a module as well, if you 
> wanted.  All you have to do is remove modules from the .kdesvn-buildrc. 
> So, 
> I think it may be appropriate for single module use as well.

Ok. For just one module, I felt no need to recommend the use of a
building script, but will change to tell the reader that it can!
 
> Also, in the recommended kdesvn-buildrc, you have cxxflags and
> make-options 
> both empty.  Which is fine, and works well (and I guess now I must make
> sure 
> it always works. ;) ), but you may want to make a comment to the effect
> that 
> they're empty on purpose.
Yes, they are empty on purpose. I will add the comment.

> Also, the description on the critical modules gives kdesvn-build more
> credit 
> than it's due at this point.  If qt-copy, arts, kdesupport, or kdelibs
> fails, 
> kdesvn-build will by default keep truckin' along, allowing every other
> module 
> to fail too.
> I could default the stop-on-failure option to true for those modules, but
> the 
> only time that the build really, really couldn't continue is if the
> critical 
> modules hadn't been installed before.  Normally kdelibs failing is OK
> since 
> it installed fine yesterday. ;)
OK, I will update the guide to reflect that. I guess I can add
stop-on-failure just to kdelibs and arts, where it makes more sense.

 
> Other than that the guide looks very helpful, and is certainly more 
> descriptive than I would have been.
Thanks for your comments, and for kdesvn-build. And BTW, I still owe you
that man page!

Next step: updating the doc-primer. This Subversion thingie better be
worth it!

Cheers,

Carlos Woelz
-- 
  Carlos Leonhard Woelz
  carloswoelz at imap-mail.com