-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
|> That is exactly the problem. You see, if we put april software update |> into consideration (these are standard openmoko apps as well), the |> prerequisite will not be small for a toolchain. I'm still thinking | | Not sure what you mean, is it that the dependencies for the April | software are different and hence the toolchains needs both April and | May libs ? | | I have just looked at one app (dialer), so you guys know the | dependencies a lot better than I do and maybe they do make the | toolchain too big, but just for the dialer the toolchain was pretty | reasonable size. | |> about this out of my personal interest. Why not allow installation of target packages into the toolchain and these "difficult philosophical questions" of what to stuff into toolchain are GONE. End users can decide and enforce what they wanted in there purely from normal distribution packages. If they want ASU stuff in there, give 'em a list of package names that form ASU, they can wget them and install them into their toolchain, even keep up to date with ASU daily like that. No other solution is gonna fix the root issue, is it! - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkg/yuQACgkQOjLpvpq7dMpdwwCgimbF0+sOU1BqkoX9IcZqD/yy LeIAnjGi7+Nnoh7Q7TlP8BUQfZz+B4a9 =aRbz -----END PGP SIGNATURE----- _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community