View Single Post
joerg_rw's Avatar
Posts: 2,222 | Thanked: 12,651 times | Joined on Mar 2010 @ SOL 3
#1067
Originally Posted by reinob View Post
Define "dropping". I suggested that



i.e. that the *dependency* be removed. All N900s need pulseaudio. Many/most N900 don't need esd. Hence esd should not be a dependency of pulseaudio, but a recommendation or suggestion or whatever you want to call it.

Every user would still have the freedom of apt-get install'ing esd or whatever other package he or she may want to install.

Personally I don't care about esd, and that's why I took it as an example. CSSU should be more "C" and less (first) "S". Open-sourced versions of Nokia closed-source programs should not be clones, they should bring improvements. Otherwise I *personally* don't care if the source code of a program is available or not (unless I want to modify it myself)

The same goes for dependencies. If Nokia decided that modest needs intellisync or exchange as a dependency, that doesn't mean that they are real dependencies, and hence CSSU should fix those dependencies and make them optional. [ This is just a ficticious example, I don't know if, but I guess that, those dependencies are actually there ]

But hey, as long as each user has the freedom to remove or install a package, what CSSU does or does not is irrelevant..
(Sorry for not shortening the quote above)

Basically that's what I'm pushing for since quite some time.
Original Nokia concept of one MetaPackage containing all was tailored to fit their idea of rolling out a complete system every once in a while, while same time Nokia doesn't need to care too much about proper dependencies - at least that's my humble guess. Now while maintaining stuff in CSSU, this MP more and more becomes an annoyance and a PITA.

So while we noticed that, Merlin1991 and me thought about a way to overcome those problems. See this IRC meeting protocol for related info about making stuff optional.
In CSSU we should strive to move more and more packages out of the MP blob and make them proper autonomous packages with a working set of dependencies.
CSSU is "seamless" (as in your definition) regarding allowing user to benefit from bugfixes while not forcing any UI/UX changes on her/him. It however is "Community" (again in your definition) in trying to allow user more freedom of choice than original Nokia MP concept did. By no way we're going to replace Nokia's set of forced components and settings by our own deemed improved set that's similarly restrictive regarding freedom of choice. In your above example, ESD would need to become an optional (original Nokia-)package, while for example the new camera-ui would become an optional-alternative CSSU package, since it replaces the original Nokia package, introduces UX changes, and fremantle needs one of both, thus "-alternative".

cheers
jOERG
__________________
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member

EX Hildon Foundation approved
Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/

IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N

Last edited by joerg_rw; 2012-11-18 at 19:02.
 

The Following 8 Users Say Thank You to joerg_rw For This Useful Post: