<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 2 Feb 2009, at 19:19, Erik Hovland wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><blockquote type="cite">SVN commit 920313 by lfranchi:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">switch to linking to libplasma from kdelibs 4.2 instead of our own. awesome!<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">this depends on kde 4.2, but i have checked with the distros and it will not<br></blockquote><blockquote type="cite">be a problem at all for 2.1 to depend on 2.2, even in a best-case-scenario<br></blockquote><blockquote type="cite">where we release in 2 months.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">As I had already explained on IRC, I request to reconsider this<br></blockquote><blockquote type="cite">commit. I do not think it wise to start depending on KDE 4.2 right<br></blockquote><blockquote type="cite">now, for a number of reasons:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">1)<br></blockquote><blockquote type="cite">KDE 4.2 was officially released on January 27 2009. In other words: a<br></blockquote><blockquote type="cite">few days ago. This is very little time.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We _are_ going to lose a number of contributors and testers because of<br></blockquote><blockquote type="cite">this. It's obvious that not all of our SVN users are necessarily using<br></blockquote><blockquote type="cite">KDE 4.2 yet.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">If someone is using an SVN prerelease version of amarok, asking for a *major<br></blockquote><blockquote type="cite">release* of KDE seems to me to be a pretty small request.<br></blockquote><br>No, but showing a bit more restraint might have been prudent. Note that not even<br>kubuntu has readily available packages for 4.2 on intrepid. So that<br>means that if<br>someone wants to now develop w/ Amarok they have to once again get on the<br>KDE source code train. Not a pleasant proposition for those of us who would<br>prefer to only work on Amarok and deal w/ its bugs.<br><br></div></blockquote><div><br></div><div>IIRC 4.2 is available on ubuntu, but i'll let someone with more ubuntu knowledge speak.</div><br><blockquote type="cite"><div>Having said that, the deal is done - I say don't revert it. Better I<br>struggle in the<br>background if the rest of the devs are already clipping away on 4.2. I am likely<br>to just not 'git svn rebase' for a couple of weeks until kubuntu catches up.<br><br><blockquote type="cite">3)<br></blockquote><blockquote type="cite">The only reason for the dependency on KDE 4.2 is currently LibPlasma.<br></blockquote><blockquote type="cite">We do have the option of importing the latest LibPlasma into Amarok,<br></blockquote><blockquote type="cite">as we used to do. Later on, we could still decide whether we want to<br></blockquote><blockquote type="cite">keep this or not; changing this would be trivial.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">yes, the reason to do this is to remove the temporary hack that is copying<br></blockquote><blockquote type="cite">libplasma in our source tree. by doing this we lose out on bugfixes, need to<br></blockquote><blockquote type="cite">make sure that things don't get out of sync, and add more work for ourselves<br></blockquote><blockquote type="cite">in the future.<br></blockquote><br>One of the reasons for the switch was because staying on the tip of plasma was<br>more trouble then the benefit of getting the bugfixes. Is anyone sure that these<br>troubles are over? I know they moved to kdelibs and have pledged a stable API,<br>but "the proof is in the pudding</div></blockquote><div><br></div><div>well they have to keep a stable API. you can't just go around breaking kdelibs ABI compatibility---it becomes a *major* issue (much more than kdebase/libs/). in fact this happened yesterday (accidental commit that broke it) and it was reverted immediately.</div><div><br></div><div>leo</div></div><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>---</div><div>Leo Franchi<span class="Apple-tab-span" style="white-space: pre; "> </span>(650) 704 3680</div><div>Tufts University 2010 </div><div><br></div><div><a href="mailto:lfranchi@kde.org">lfranchi@kde.org</a></div><div><a href="mailto:leonardo.franchi@tufts.edu">leonardo.franchi@tufts.edu</a></div></div></div></div></div></div></span></div></span></div></span></div></span> </div><br></body></html>