I would not hold my breath. The Nokia repository contains mostly proprietary Nokia packages without a source code. The only two ways to replace them in CSSU are, 1) write them from scratch and hope they do the same thing, or 2) reverse engineer them. The latter has shown a few first swallows (e.g. MCE) but, as we all know, that does not necessarily a summer make. If you want to know more, head down to the FPTF thread to get an idea about the scale of the task.
I would not hold my breath. The Nokia repository contains mostly proprietary Nokia packages without a source code. The only two ways to replace them in CSSU are, 1) write them from scratch and hope they do the same thing, or 2) reverse engineer them. The latter has shown a few first swallows (e.g. MCE) but, as we all know, that does not necessarily a summer make. If you want to know more, head down to the FPTF thread to get an idea about the scale of the task.
Wouldn't a "good enough" fix just be to update the CSSU installation instructions to include a step that redirects the repositories sources to a working copy of the Nokia repos? It wouldn't replace them, of course, but would get the user past that "showstopping" error in the install process.
Wouldn't a "good enough" fix just be to update the CSSU installation instructions to include a step that redirects the repositories sources to a working copy of the Nokia repos? It wouldn't replace them, of course, but would get the user past that "showstopping" error in the install process.
The "good enough" solution would be to put all of the FOSS packages that used to be on Nokia repo (and there are plenty of them) on maemo.org repositories. That was discussed with merlin1991 (CSSU maintainer) and I guess he'll do it rather soon than later.
