<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Consolas'; font-size:11pt; font-weight:400; font-style:normal;">On Sunday 11 January 2009, Allen Winter wrote:<br>
> Howdy,<br>
><br>
> I'd like to start making some more external packages required instead of<br>
> optional. For example, in kdepimlibs I really like to start requiring<br>
> cyrus-sasl and openldap.<br>
><br>
> I think these packages provide basic functionality rather than "extra and<br>
> cool" stuff.<br>
><br>
> Objections to making sasl and openldap build-time requirements in<br>
> kdepimlibs?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Well it always just goes back to the tradeoff of developer time and interest. If no developer wants to maintain kdepim where openldap and cyrus-sasl is optional then I think they should be made required (or at least very clearly marked that compiling without is unsupported).<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>On the other hand, if there are people who will put in the time to ensure that openldap and/or cyrus-sasl is optional I don't see why we should not go along. <br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>But in short though, sounds good to me.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Regards,<br>
- Michael Pyne</p></body></html>