<p>that sounds like a really good idea. Today I've tried the 0.8.3 installer and it worked out really well (althought it has forgotten to add the strigi dependency).</p><p>Atm the update function is a bit rusty implemented in the interface but ok.. that's easy to change.
</p><p>I wonder if there's any chance that I could upload the code somewhere because I fear that I won't have much time to work on it. Further more I don't think I've got the skill for doing this alone. (I've just started with QT and KDE programming). So everybody who wants can work on it.
<br>sounds</p><p>Also I don't know yet how the release team is going to manage the release for windows. Will there be such updates like you get in openSUSE? (e.g. kdebase-3.96-10.1 --> kdebase-3.96-10.2) or isn't there enough server capacity to do this? If that isn't the case I have real doubts for the importance of an update feature because if you can just upgrade from
4.0 to 4.1 it will broken to a big percentage because much has changed.</p><p>As I've stated in the first email I don't know these things yet and I would appreciate if someone could tell me (if it's already decided)
</p><p><br></p><div><span class="gmail_quote">2007/11/20, Ralf Habacker <<a href="mailto:ralf.habacker@freenet.de">ralf.habacker@freenet.de</a>>:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
Bernhard schrieb:<br>> so.. I've just checked out the svn directory of the kde-windows-installer.<br>> If I'm not completely mistaken I can use the whole stuff from the shared<br>> folder in the updater.
<br>><br>yes, but if you like to create a full updater you need more files at<br>least the settings class to get current mirror/proxy and other settings<br>> I've seen there are also plans to implement an update feature in the
<br>> kde-windows-installer. Is there something going on atm?<br>><br>Yes it was in the pipeline already for some time and is mostly<br>implemented in the installer. See the last release.<br>> Would it be better if I could somehow try to hack the update function into
<br>> the kde-windows installer or would you like it more to have two seperate<br>> programs?<br>><br>What do you think about to split the task: the installer handles all<br>update related stuff and a little tray icon program which is loaded up
<br>on login and checks in regulary intervals for updates (the way how to<br>detect has to be designed, the related code should be in the shared<br>folder - any suggestions) and if updates are available<br>it runs the installer with a specific command line to perform the
<br>required steps.<br><br>Ralf<br><br>> 2007/11/13, Bernhard <<a href="mailto:mustermaxi@gmail.com">mustermaxi@gmail.com</a>>:<br>><br>>> thx for the feedback!<br>>><br>>> To be honest I've hoped that someone could make a nice suggestion because
<br>>> I don't know how the KDE team will manage the whole packaging. (compiled<br>>> packages, just source, executables) Afaik you won't release a KDE Windowsversion with KDE<br>>> 4.0. Is this still true?
<br>>><br>>> The whole project has basically begun because I think it would be a nice<br>>> addition for users who are currently using a program, are encountering a<br>>> bug, file a bug report, and if you've got luck with the next update (you get
<br>>> from this little prog) you get the fixed version automatically. (don't know<br>>> if you should just update for example from 4.0.0 to 4.0.1 or if you should<br>>> use snapshots of svn.)<br>>> I'm open for every suggestion regarding both technical and user views.
<br>>><br>>> If there's no other way round I thought about just downloading the new zip<br>>> archives and replace the files of your current install.<br>>><br>>> Sadly I haven't had any time yet to look into the code of the KDE-Windowsinstaller and how it works. Does it compile something? Or does it just copy
<br>>> the files from the archive into your install directory?<br>>><br>>> Also I don't know yet how to implement the dependency handling and if this<br>>> is something my program should concern about (imo the dependencies should
<br>>> have already been checked by kde-windows-installer).<br>>><br>>> I hope you've got some suggestions and feedback for me.<br>>><br>>> Bernhard<br>>><br>>> 2007/11/13, Ralf Habacker <
<a href="mailto:ralf.habacker@freenet.de">ralf.habacker@freenet.de</a>>:<br>>><br>>>> Bernhard schrieb:<br>>>><br>>>>> I've attached a new version of the "mockup". It should just show
<br>>>>><br>>>> what's in<br>>>><br>>>>> my mind .. atm.<br>>>>><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/">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/">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">Kde-windows@kde.org</a><br>>>> <a href="https://mail.kde.org/mailman/listinfo/kde-windows">
https://mail.kde.org/mailman/listinfo/kde-windows</a><br>>>><br>>>><br>>><br>><br>><br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________
<br>> Kde-windows mailing list<br>> <a href="mailto:Kde-windows@kde.org">Kde-windows@kde.org</a><br>> <a href="https://mail.kde.org/mailman/listinfo/kde-windows">https://mail.kde.org/mailman/listinfo/kde-windows</a>
<br>><br><br>_______________________________________________<br>Kde-windows mailing list<br><a href="mailto:Kde-windows@kde.org">Kde-windows@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/kde-windows">https://mail.kde.org/mailman/listinfo/kde-windows
</a><br></blockquote></div><br>