< Projects | KDE on Windows | Meetings Revision as of 09:40, 28 July 2012 (view source)SaroEngels (talk | contribs) (→Things to hack on)← Older edit Revision as of 09:45, 28 July 2012 (view source) SaroEngels (talk | contribs) (→Things to hack on)Newer edit → Line 30: Line 30: * Removing Version numbers from filenames in emerge * Removing Version numbers from filenames in emerge * Let's build the frameworks? * Let's build the frameworks? +* kdewin-app-installer * Website * Website Revision as of 09:45, 28 July 2012 The KDE Windows community will meet in Osnabrück on the weekend of 3.- 5. August The meeting will take place at the Intevation offices in Osnabrück. For organization and to participate please check the Sprint Page Proposed Topics Qt5 --> Andy? KDE frameworks --> Patrick? Packaging / NSIS / MSI how to integrate in emerge even better. "Autoupdates" for Standalone software like Kontact / Amarok / Calligra Sandboxing Oxygen or a more Native look as the default? Tests / Unittests (Maybe more of a "to hack" on topic, but It would be cool if we could make better use of them) Keyword system to tagging unstable software: Gentoos emerge uses "accept keywords" to categorize versions of software into either stable, testing or experimental. I'd like to propose a similar (but simpler) system for emerge on Windows: Add a "keyword" parameter to installation targets. If empty / not existant (current situation) that means "safe" (stable). Potentially unstable packages could then be tagged as potentially dangerous by giving them a certain keyword (like "~"). An emerge configuration option would be needed that defines the keywords that the user accepts (per default, that'd be empty - accepting all current targets but not those marked as unstable). Developers that want to run bleeding edge software could just add the "~" keyword to the list of accepted ones and instantly move up to all the latest releases (which also makes sense as they might depend on each other). This simple approach would not have any regressions or require a large initial "tagging" effort but would allow developers in the future to mark potentially dangerous targets leading to a nicer experience for e.g. app developers that "just want a stable base to start from". Things to hack on Update mingw-w64 to gcc 4.7 as 4.6 is required by Qt 5 Patch Mysql to build with mingw Removing Version numbers from filenames in emerge Let's build the frameworks? kdewin-app-installer Website Retrieved from "https://techbase.kde.org/index.php?title=Projects/KDE_on_Windows/Meetings/Osnabrück_Meeting_Summer_2012&oldid=74052" Content is available under Creative Commons License SA 4.0 unless otherwise noted.