-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
| The strategy above allows us to easily add and remove packages while | maintaining stable end-user systems. Until the dust settles on the But so does a single kernel package that includes the modules. There can be no risk of having modules mismatch the monolithic kernel then. Nor will changing to this model "destabilize" anything, the package is sticking things down /lib/modules same as the modular packages do using the same code in the packaging app. You won't find when you are away from a network connection you would have liked those ppp-related modules after all either. | kernel/modules packaging, I suggest we do the above to be as safe as | possible. Current setup seems unstable IMO because it indirects through the whole packaging system, bloating the work done there. The only thing that makes sense about it is that is reduces footprint on storage when we consider all the modules, but bulk of users do not want to have to care about package selection to this degree, they will go with whatever default package set is. Anyway this is up to the packaging guys, but I would stick it all in one package and have done with it, making folks' updates faster as a side effect. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiS/DsACgkQOjLpvpq7dMrIUQCfSQgRyVH35rglbjpMpa9yZaAG LGwAn37dz7Ou3SvHr2i2NOglz2G5RCQp =dBqC -----END PGP SIGNATURE----- _______________________________________________ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support