Alexander E. Patrakov wrote these words on 02/08/06 22:52 CST:
> But it is indeed better to say "no" to UTF-8 support now, because of
> BLFS issues and because UTF-8 support is a property of the whole system,
> not just its base. The blacklist approach ("If a package is not listed
> here, it me
Alexander E. Patrakov wrote these words on 02/08/06 22:52 CST:
> The blacklist approach ("If a package is not listed
> here, it means there are no known locale specific issues or problems
> with that package" on
> http://www.linuxfromscratch.org/blfs/view/svn/introduction/locale-issues.html)
>
Randy McMurchy wrote:
IMO he isn't blaming BLFS for problems with UTF-8. Alexander has
publically stated that after adding UTF-8 to LFS, that maybe it really
isn't ready for the main book. Even asking to revert it or put it in an
experimental branch.
http://archives.linuxfromscratch.org/m
Alan Lord wrote:
Alan, sorry for not getting to this sooner in BLFS, life has once
again stepped in the way. :-/ Unfortunately, I don't see it any
time in the next couple of weeks unless another editor can grab it.
If it wouldn't be too much trouble, when the build completes, would
you mind post
Justin R. Knierim wrote these words on 02/09/06 09:50 CST:
> IMO he isn't blaming BLFS for problems with UTF-8.
Then you and I read plain English differently. IMO, the following
statement directly conflicts with what you say above:
"But it is indeed better to say "no" to UTF-8 support now, becau
Randy McMurchy wrote:
Justin R. Knierim wrote these words on 02/09/06 09:50 CST:
IMO he isn't blaming BLFS for problems with UTF-8.
Then you and I read plain English differently. IMO, the following
statement directly conflicts with what you say above:
Arg, need to re-read emails be
Justin Knierim wrote:
> There
> are other problems, such as people not wanting the bloat, english
> speakers not seeing the need, etc.
Just to clarify: As an English (only) speaker, I really don't want
UTF-8 on *my* system. As a BLFS developer, I certainly understand the
desire and need for U
On Thu, Feb 09, 2006 at 10:50:44AM -0600, Bruce Dubbs wrote:
> My only problem with LFS on the issue is that LFS traditionally has not
> offered choices. That is, there is only "one true path" through the
> book. This makes users who do not need or want UTF-8 proceed on their
> own. IMO, this is
I know - posting to my own message but...
Just d/l the OOo linux-intel-x86 package and it's all in bloody RPMS!!!
Aghh
Oh well looks like I will be building from source somehow - now where
did I put audiolib.h...
Al
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ:
Alan Lord wrote:
> Bruce Dubbs wrote:
>
>> Alan,
>> I'm just curious where you have the {audio,sound}lib.h files located.
>> In my system I have:
>>
>> $ locate audiolib.h
>> /usr/X11R6/include/audio/audiolib.h
>> $ locate soundlib.h
>> /usr/include/alsa/asoundlib.h
>> /usr/include/sys/asoundli
Alan Lord wrote:
> I know - posting to my own message but...
>
> Just d/l the OOo linux-intel-x86 package and it's all in bloody RPMS!!!
If you convert the RPMS to tar.gz with rpm2targz then the tar.gz's will
unpack to /opt/openoffice.org2.0.
http://downloads.linuxfromscratch.org/rpm2targz.t
Jeremy Huntwork wrote:
On Thu, Feb 09, 2006 at 10:50:44AM -0600, Bruce Dubbs wrote:
My only problem with LFS on the issue is that LFS traditionally has not
offered choices. That is, there is only "one true path" through the
book. This makes users who do not need or want UTF-8 proceed on the
Jeremy Huntwork wrote:
And to further clarify, an LFS machine as it currently is does *not*
automatically use UTF-8. The changes to the LFS book are so that the
LFS system *can* use UTF-8 properly if a user requires it. IMO, this is
I'd like some clarification on one point then. IIRC, I read
Joel Miller wrote:
Jeremy Huntwork wrote:
And to further clarify, an LFS machine as it currently is does *not*
automatically use UTF-8. The changes to the LFS book are so that the
LFS system *can* use UTF-8 properly if a user requires it. IMO, this is
I'd like some clarification on one point
Joel Miller wrote:
Jeremy Huntwork wrote:
And to further clarify, an LFS machine as it currently is does *not*
automatically use UTF-8. The changes to the LFS book are so that the
LFS system *can* use UTF-8 properly if a user requires it. IMO, this is
I'd like some clarification on one point
Bruce Dubbs wrote:
They come form the nas package.
http://www.linuxfromscratch.org/blfs/view/cvs/multimedia/nas.html
-- Bruce
Thanks Bruce, but I thought by adding --without-nas I wouldn't need
them? Perhaps they are a dependency anyway...
--
http://linuxfromscratch.org/mailman/listin
Chris Staub wrote:
Joel Miller wrote:
Jeremy Huntwork wrote:
And to further clarify, an LFS machine as it currently is does *not*
automatically use UTF-8. The changes to the LFS book are so that the
LFS system *can* use UTF-8 properly if a user requires it. IMO, this is
I'd like some clarif
Joel Miller wrote:
I'd like some clarification on one point then. IIRC, I read in a post by
Alexander that the changes to the book made it so that ssh would no
longer connect properly to non UTF-8 systems. In order to do that you
had to run ssh through screen. This would be a *massive* inconven
Jeremy Huntwork wrote:
I tried looking for the error using a recently built LFS LiveCD. I've
been using en_US.UTF-8 as a locale with it recently, and ssh both
incoming and outgoing has worked fine for me.
Logging in is fine. Once you are in, try "su - root".
Justin
--
http://linuxfromscratc
Dan Nicholson wrote these words on 02/09/06 16:58 CST:
> On 2/9/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>>1. Not put dvd_rw-tools in BLFS.
>
> No, I think it should be in there.
We agree on this point. I believe DJ offered an opinion on this
as well that dvd+_rw-tools should be in the book.
Justin R. Knierim wrote:
Jeremy Huntwork wrote:
I tried looking for the error using a recently built LFS LiveCD. I've
been using en_US.UTF-8 as a locale with it recently, and ssh both
incoming and outgoing has worked fine for me.
Logging in is fine. Once you are in, try "su - root".
Worke
Jeremy Huntwork wrote:
Worked fine here... I will note that, seeing that I'm using a german
locale, my keys were a bit askew. The 'z' and the 'y' were reversed
and the '-' was where the '/' key is. Other than that, it worked fine.
Hmm, strange. I wasn't using the German profile when I report
Justin R. Knierim wrote:
Hmm, strange. I wasn't using the German profile when I reported that
problem, it was the normal en_US.UTF-8. Anyways, I'll try it again
tonight and see what I can find.
Nevermind, I just tried with the 6.2-pre3 LiveCD and I can't reproduce
the error either. Sorry
23 matches
Mail list logo
