<p>so.. I've just checked out the svn directory of the kde-windows-installer. If I'm not completely mistaken I can use the whole stuff from the shared folder in the updater.</p><p>I've seen there are also plans to implement an update feature in the kde-windows-installer. Is there something going on atm?
</p><p>Would it be better if I could somehow try to hack the update function into the kde-windows installer or would you like it more to have two seperate programs?<br></p><br><div><span class="gmail_quote">2007/11/13, Bernhard <
<a href="mailto:mustermaxi@gmail.com">mustermaxi@gmail.com</a>>:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex"><p>thx for the feedback!</p><p>To be honest I've hoped that someone could make a nice suggestion because I don't know how the KDE team will manage the whole packaging. (compiled packages, just source, executables) Afaik you won't release a KDE
<span id="st" name="st" class="st">Windows</span> version with KDE
4.0. Is this still true?<br></p><p>The whole project has basically begun because I think it would be a nice addition for users who are currently using a program, are encountering a bug, file a bug report, and if you've got luck with the next update (you get from this little prog) you get the fixed version automatically. (don't know if you should just update for example from
4.0.0 to 4.0.1 or if you should use snapshots of svn.) <br>I'm open for every suggestion regarding both technical and user views.</p><p>If there's no other way round I thought about just downloading the new zip archives and replace the files of your current install.
</p><p>Sadly I haven't had any time yet to look into the code of the KDE-<span id="st" name="st" class="st">Windows</span> installer and how it works. Does it compile something? Or does it just copy the files from the archive into your install directory?
</p><p>
Also I don't know yet how to implement the dependency handling and if this is something my program should concern about (imo the dependencies should have already been checked by kde-<span id="st" name="st" class="st">
windows</span>-installer).</p><p>I hope you've got some suggestions and feedback for me.
</p><p>Bernhard</p><br><div><span class="gmail_quote">2007/11/13, Ralf Habacker <<a href="mailto:ralf.habacker@freenet.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">ralf.habacker@freenet.de
</a>>:</span><div><span class="e" id="q_1163951afb04c37c_1"><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
Bernhard schrieb:<br>> I've attached a new version of the "mockup". It should just show what's in<br>> my mind .. atm.<br>><br>This looks good. What are your plans about the package format used for
<br>updates ? Currently there are only full packages available<br><a href="http://download.cegit.de/kde-windows/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://download.cegit.de/kde-windows/
</a><br><br>BTW: You may take a look on the recent kde on windows installer located
<br>on <a href="http://websvn.kde.org/trunk/kdesupport/kdewin-installer/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://websvn.kde.org/trunk/kdesupport/kdewin-installer/</a>. May be some<br>
stuff can be merged.<br><br>regards<br> Ralf<br>_______________________________________________
<br>Kde-windows mailing list<br><a href="mailto:Kde-windows@kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Kde-windows@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/kde-windows" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
https://mail.kde.org/mailman/listinfo/kde-windows</a><br></blockquote>
</span></div></div><br>
</blockquote></div><br>