|
From: | Cyril Roelandt |
Subject: | Re: Google Summer of Code project concepts |
Date: | Thu, 11 Apr 2013 21:38:34 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 |
On 04/09/2013 04:00 PM, Nikita Karetnikov wrote:
That's a fair question. I suppose I don't much know -- the Summer of Code ideas site listed "package window manager" as one of the projects, so I assumed there was a lot to be done. Maybe that's more about packaging the dependencies of the larger projects.I've just checked the page. Yes, I feel that it's about packaging the dependencies. So if you like tiling WMs, you can package one (by the way, there is a patch [1] that adds dwm to 'core-updates'). Then you can package things like PDF viewers and other graphical tools. For example, you can create a list of tools which are shipped with GNOME. This will reduce the amount of work when we decide to package a non-tiling WM.
Indeed, this project is more about packaging a __Desktop_Environment__ rather than a simple Window Manager.
By the way, I pushed the dwm patch in the core-updates branch.
So, here is a to-do list that summarizes the above: 1. Choose a WM. 2. For instance, find which packages are shipped with GNOME. 3. Use 'guix import' and 'guix package -A' to identify the missing packages. It will help to determine what should be done first.
One thing to do for huge packages such as GNOME/KDE would be to package the graphic toolkits they use, and which are used by many pieces of software. This would probably require quite a lot of work.
Cyril.
[Prev in Thread] | Current Thread | [Next in Thread] |