Jim Gifford wrote: > This discussion needs to happen on both lfs-dev and cross-lfs, everyone > in lfs-dev seems to want it, but people in cross-lfs don't need it.
Are you saying that because people are cross-compiling, they won't need UTF-8? That can't be right... > > Talking to community members in cross-lfs, most of them don't want to be > forced to use utf-8, because they don't need it. Others want to be able > to test it, and if they don't like it do a build without it. I think this viewpoint is a little skewed. From my understanding we're not *building* UTF-8. We're making sure all our packages support that already built and existing locale. Really, it's what upstream devs should be focusing on doing anyway. We're just making sure that everything is compatible. If the problem comes from adding a database program into LFS (which many of us end up building anyway) so that we can get proper man-page generation for all locales in LFS, then as you've already implied, let's start working on a solution that would allow us to drop DB. IMHO, that's all that needs to be done. Apart from that one package, we're not *building* anything extra into LFS. What other 'extras' are there that you object to? If I am misunderstanding something, then you have my apologies, and feel free to set me straight. -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
