> One of the biggest reason not to go down the path of eglibc and/or others, is that we can build the exact same software stack for all the hardware (netbooks, nettops, even laptops and desktop PCs) quicker and easier on glibc. This creates a development atmosphere where everything just works, we only need to support one libc variant etc.
I don't think glibc is wrongly picked and I'd like to see if someone can give more information between them since some big distributions move toward eglibc. BTW, I think they are very compatible to each other so that eglibc can be used in all. Yes, we definitely should support only one libc. > Some of the arguments posted on that blog site you link are really weak BTW, e.g. the 'bash' ones, -Os. Yes, these are week reasons if they are true. I didn't follow all eglibc discussions because there are so many but I think there has to be reasons to switch to eglibc, though MeeGo isn't necessary to do so until we figure out it really benefits the project.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
