Re: [Fwd: Re: UTF-8]

Alexander E. Patrakov([EMAIL PROTECTED])@Sat, Jan 21, 2006 at 11:45:50AM +0500: > Chris Staub wrote: > > >I don't think anyone is debating that they aren't being forced to use > >UTF-8 locales. However, the issue is that if you never do use a UTF-8 > >locale, then the UTF-8 code just sits there un

Re: [Fwd: Re: UTF-8]

Chris Staub wrote: I don't think anyone is debating that they aren't being forced to use UTF-8 locales. However, the issue is that if you never do use a UTF-8 locale, then the UTF-8 code just sits there unnecessarily taking up space. It isn't a question of whether it "works" - I *know* that non-

Re: Man 1.6 + UTF-8

I wrote: The good default would be (assuming the Debian-specific manual page encoding, -Tlatin1 default nroff argument, and the "less -isR" pager that is able to convert from ISO-8859-1 to UTF-8 on the fly): TRANSLATIONS 8bit:da:de:en:es:fi:fr:ga:gl:id:is:it:nb:nl:nn:no:pt:sv HARDCOPY_TRANSLAT

Re: Man 1.6 + UTF-8

Federico Lucifredi wrote: (please CC: at least lfs-dev) Hello Jim, Alex, Yes, I have plans for (1) and (2), so there should be no particular problem getting that fixed. I have not thought extensively of the interaction problems with groff, tho, so that is next on the list. for (3), I would like

Re: Man and Groff - Author Feedbacks - UTF-8 Comments

Werner LEMBERG wrote: I have checked out today's Groff from Savannah CVS. The test results are below. 2) The relocation stuff segfaults, so I had to disable it by editing src/libs/libgroff/Makefile.sub. Backtrace, please, or give a recipe to repeat it. Make sure that /opt/groff/bin

Re: UTF-8

Jeremy Herbison wrote: How about just a "I don't wanna use man-db" hint, with maybe a link and a warning on the man-db page. Short version below. Works in all locales with groff-1.19.2. Not for the book, because it blacklists Russian manual pages. == cut here == You need Man-1.5b a

aboutsbus.xml

As a part of my maintenance, I decided to give the SBU Home PAge its own address. The new address is http://www.linuxfromscratch.org/~sbu/ The old site still works too, but I'd like to change it in the book. Here is a patch. -- Bruce Index: chapter04/aboutsbus.xml ===

Re: List of package urls

On Jan 15, 2006, at 4:04 PM, Richard A Downing wrote: Oh! I thought it was so clever-clogs could get a later (and greater, of course) version if he wanted, and then bombard the support list with questions about why his system is screwed :-) "I suppose the reason I was having problems was c

Re: RFC: Implementing Trac [long]

Matthew Burgess wrote: > > 7) There is no "Read" link in the menu bar described above. How does > putting the rendered version of the book on the wiki.l14h.org site get > handled by Trac - is it just a couple of Rewrite rules or similar to > request that Trac just passes handling of serving the s

Re: Package doc

Randy McMurchy wrote: > go moko wrote these words on 01/20/06 15:04 CST: > > >>For some packages of the book, all the doc is >>explicitely installed in >>/usr/share/doc/-. >>But for others, like Pango or ATK, the --with-html-dir >>tag of configure is not used for this in the book's >>commands, an

Re: RFC: Implementing Trac [long]

Jeremy Huntwork wrote: Well, the signal to noise ratio in this thread was probably the lowest I've seen for a long time on this list. To say I'm disappointed in the behaviour/attitude of certain contributors would be putting it very mildly indeed. That aside, here are my thoughts on Tra

Re: [Fwd: Re: UTF-8]

On 1/20/2006 13:45, Chris Staub wrote: > non-UTF-8 locales will work fine with UTF-8-enable LFS - it's that if > the extra disk space and memory being taking up is not needed, then it > shouldn't be there. I think this is sort of like saying well my DNS box has/needs only a small disk in it, why s

Re: UTF-8

Matthew Burgess wrote: Jim Gifford wrote: Matt what I would like to do is hold off until LFS gets more testing done, then merge. Is that acceptable. Of course, just so long as you haven't written UTF-8 off for CLFS completely :-) Regards, Matt. No we have started to experiment with test b

Re: UTF-8

Jim Gifford wrote: Matt what I would like to do is hold off until LFS gets more testing done, then merge. Is that acceptable. Of course, just so long as you haven't written UTF-8 off for CLFS completely :-) Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://

Re: UTF-8

Matthew Burgess wrote: I'd obviously prefer CLFS to follow suit - cross-building and UTF-8 are (or should be) entirely orthogonal concepts. If our adding support for UTF-8 breaks the CLFS build, then we should work together to see if an amicable solution is possible. Matt what I would like

Package doc

Hi For some packages of the book, all the doc is explicitely installed in /usr/share/doc/-. But for others, like Pango or ATK, the --with-html-dir tag of configure is not used for this in the book's commands, and so, the doc isn't versionned. I know it's a detail, and that users can do './configu

Re: Overcomplicated? [part 1: glibc, coreutils]

Alexander E. Patrakov wrote: there are claims that the current instructions are overly complicated. Below is the first part of the proof that they are in fact needed, but still insufficient for producing a system that works with both UTF-8 based and traditional locales with zero regressions, a

Re: UTF-8

Jim Gifford wrote: With the recent thread in Cross-LFS and LFS-dev lists, I wanted to pose an idea. Couldn't we add the utf-8 pages to an appendix and refer to them via notes in the builds, like we currently do with Cracklib in Shadow, the only difference is that we would be refering to an appe

Re: Man and Groff - Author Feedbacks - UTF-8 Comments

> I have checked out today's Groff from Savannah CVS. The test results are > below. > > 2) The relocation stuff segfaults, so I had to disable it by editing > src/libs/libgroff/Makefile.sub. Backtrace, please, or give a recipe to repeat it. > groff -K KOI8-R -Tutf8 -mandoc /usr/share/man/ru/ma

Re: UTF-8

So, if you're following this thread and you have a strong feeling that you'd like the UTF-8 changes to be added in as the default or prefer them to be stored in an appendix, please make your opinion known. -- Dan Yes to default please. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev F

Re: UTF-8

Chris Staub wrote: Patrakov also mentioned something about ncurses apps taking an extra 16kb of RAM. Yeah, I remember him saying that also. For the life of me I can't find anything in the mailing list archives though. He said (paraphrasing) that the binaries were identical with ncurses app

Re: UTF-8

Chris Staub wrote: > I don't think anyone is debating that they aren't being forced to use > UTF-8 locales. However, the issue is that if you never do use a UTF-8 > locale, then the UTF-8 code just sits there unnecessarily taking up > space. It isn't a question of whether it "works" - I *know* that

Re: UTF-8

On 1/20/06, Chris Staub <[EMAIL PROTECTED]> wrote: > > I don't think anyone is debating that they aren't being forced to use > UTF-8 locales. However, the issue is that if you never do use a UTF-8 > locale, then the UTF-8 code just sits there unnecessarily taking up > space. It isn't a question of

Re: UTF-8

Chris Staub wrote: M.Canales.es wrote: El Viernes, 20 de Enero de 2006 17:34, Jim Gifford escribió: 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

[Fwd: Re: UTF-8]

Original Message Subject: Re: UTF-8 Date: Fri, 20 Jan 2006 13:45:28 -0500 From: Chris Staub <[EMAIL PROTECTED]> To: Cross-LFS Discussion List <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> M.Canales.es wrote:

Re: UTF-8

El Viernes, 20 de Enero de 2006 17:34, Jim Gifford escribió: > 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. No one is forcing to use

Re: UTF-8

On 1/20/06, Jim Gifford <[EMAIL PROTECTED]> wrote: > Tushar Teredesai wrote: > > On 1/20/06, Jim Gifford <[EMAIL PROTECTED]> 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. > >> That's w

Re: RFC: Implementing Trac [long]

Jeremy Huntwork wrote: > Jeremy Huntwork wrote: > >>So, my plan is to manually add the 'Opened' time to the 'Last modified' >>field in the bugs database. Any objections? > > > I made this change on the backup database on anduin: > > 'update bugs set delta_ts=creation_ts where delta_ts="-00-

Re: Perl security vulnerability

On 1/20/06, Steve Prior <[EMAIL PROTECTED]> wrote: > > For existing installations, is there a way to upgrade Perl using CPAN or > is it a manual install? I'm just looking for the easiest approach, but > I can certainly do it manually. I have no idea. I don't use CPAN, though. I'm just going to

Re: UTF-8

Richard A Downing wrote: > On Fri, 20 Jan 2006 06:34:20 -0800 > Dan Nicholson <[EMAIL PROTECTED]> wrote: >>Before you spend a lot of time making changes that move the UTF-8 >>fixes to an appendix, I think we should see if that's actually what >>the community wants. Jim and a few others have said

Re: UTF-8

On Fri, 20 Jan 2006 09:45:34 -0500, Jeremy Huntwork wrote: > Richard A Downing wrote: >> On Fri, 20 Jan 2006 06:34:20 -0800 >> Dan Nicholson <[EMAIL PROTECTED]> wrote: >>>BUT, in the past when it was being decided if the book would become >>>UTF-8 compatible, I remember there being a lot of suppor

Re: UTF-8

Bryan Kadzban wrote: > If that means we need to use man-db + BDB, I have no problem with that. > But if others do take issue with adding those packages, then I'm also OK > with waiting a couple months until plain old man and groff work in UTF-8. By the time we're ready to branch for testing, that

Re: UTF-8

Jim Gifford wrote: > know all the in's and out's. Alex did do some testing, but none of the > lfs-dev's have tested it That depends on what you mean by testing. I have built it at least twice and have used the resultant english UTF-8 locale, albeit briefly. Keep in mind that it's not like we've pu

RE: UTF-8

> Jim said: > 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. No one is being forced to use utf-8. They're just building a utf-8 compati

RE: UTF-8

> I give a +1 now. The support issues alone, such as "I built non-utf8, > how can I add it now?", are enough to make me want it default on. The > alternative solutions, such as an appendix, won't solve this support > issue either. Having two separate books seems like a waste. For now, > Alexand

Re: UTF-8

Tushar Teredesai wrote: On 1/20/06, Jim Gifford <[EMAIL PROTECTED]> 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. That's why I started the thread on both lists. Why the division? I thou

Re: UTF-8

On Fri, Jan 20, 2006 at 06:34:20AM -0800, Dan Nicholson wrote: > So, if you're following this thread and you have a strong feeling that > you'd like the UTF-8 changes to be added in as the default or prefer > them to be stored in an appendix, please make your opinion known. +1 for "make UTF-8 capa

Re: cp -r to copy recursively (but not symlinks)

On Fri, 20 Jan 2006 17:18:56 +0100, Randy McMurchy wrote: > 7. Now using *one* command only, copy all these files and directories > into the test directory you created earlier. Creating symlinks in the > destination directory doesn't count. You must create actual files in > the test directory. One

Re: cp -r to copy recursively (but not symlinks)

At 06-01-20 17:18, you wrote: So, in an attempt to create directions for the book that are as efficient as possible, I'm going to lay out what I cannot do and see if any of you wouldn't mind showing me the proper syntax for the cp command to copy some files. 7. Now using *one* command only, co

Re: UTF-8

On Fri, 20 Jan 2006 08:49:56 -0800 Jim Gifford <[EMAIL PROTECTED]> wrote: > Please reply to both lists > Jim, Cross-lfs is not on gmane. Can you get it on there please, then I'll monitor it. I don't do mailing lists anymore. R. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: ht

Re: UTF-8

On 1/20/06, Jim Gifford <[EMAIL PROTECTED]> 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. > That's why I started the thread on both lists. Why the division? I thought cross-lfs was just a way o

Re: cp -r to copy recursively (but not symlinks)

Tushar Teredesai wrote these words on 01/20/06 10:42 CST: > cp -RL Linux*/include/* ~/td > > I didn't go thru the entire e-mail (currently at work) but I think > that's what you are looking for. Yes, it works. And I would have sworn I tried that combination last night when I was testing. Apparen

Re: UTF-8

Jeremy Huntwork wrote: 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...

Re: UTF-8

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 member

Re: RFC: Implementing Trac [long]

Jeremy Huntwork wrote: > So, my plan is to manually add the 'Opened' time to the 'Last modified' > field in the bugs database. Any objections? I made this change on the backup database on anduin: 'update bugs set delta_ts=creation_ts where delta_ts="-00-00 00:00:00";' It fixed the problem. S

Re: Perl security vulnerability

On Fri, 20 Jan 2006 15:45:27 +0100, Dan Nicholson wrote: > It's in the errata http://www.linuxfromscratch.org/lfs/errata/stable/ > > Thanks, Tim. My pleasure. Good to know it has been taken care of. Tim -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org

Re: UTF-8

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. That's why I started the thread on both lists. Talking to community members in cross-lfs, most of them don't want to be forced to use utf-8, because they

Overcomplicated? [part 4: kernel and bootscripts ]

I wrote: Bootscripts and kernel will go tomorrow. Sorry, I had no time to do this post properly. Reply if you actually need more details. This thread acknowledges the kernel problem: http://forums.gentoo.org/viewtopic-t-221588.html The "console" bootscript was modelled after the old one p

cp -r to copy recursively (but not symlinks)

Hi all, I have run into something that in almost 20 years of playing around with Unixes, I've never run into. I cannot get the cp command to behave nicely. I suppose it is just me being stupid and not seeing the obvious, or working too late into the night, but I'll be damned if I can figure it out

Re: Perl security vulnerability

Jeremy Huntwork wrote: Dan Nicholson wrote: It's in the errata http://www.linuxfromscratch.org/lfs/errata/stable/ It's also been added to trunk. :) -- JH For existing installations, is there a way to upgrade Perl using CPAN or is it a manual install? I'm just looking for the easiest app

Re: RFC: Implementing Trac [long]

Bruce Dubbs wrote: > > No. It just means that there was a glitch that needs to be worked out > as a part of the conversion. We won't (can't) upgrade to the new system > until all such problems are worked out. I think I found the problem. (Btw, I was pinging the wrong bug in blfs-bugs. I thought

Re: UTF-8

Alexander E. Patrakov wrote: There should be only one set of build instructions, and identical binaries. No optional appendix with commands. All differences between UTF-8 and non-UTF-8 installations should be in the /etc directory. I give a +1 now. The support issues alone, such as "I built

Re: UTF-8

On 1/20/06, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote: > I already made it known in other threads. Just in case, once again: > > There should be only one set of build instructions, and identical > binaries. No optional appendix with commands. All differences between > UTF-8 and non-UTF-8 inst

Re: UTF-8

On Fri, 20 Jan 2006 19:47:54 +0500 "Alexander E. Patrakov" <[EMAIL PROTECTED]> wrote: > Dan Nicholson wrote: > > >So, if you're following this thread and you have a strong feeling > >that you'd like the UTF-8 changes to be added in as the default or > >prefer them to be stored in an appendix, ple

Re: UTF-8

Dan Nicholson wrote: So, if you're following this thread and you have a strong feeling that you'd like the UTF-8 changes to be added in as the default or prefer them to be stored in an appendix, please make your opinion known. I already made it known in other threads. Just in case, once agai

Re: Perl security vulnerability

Dan Nicholson wrote: > It's in the errata http://www.linuxfromscratch.org/lfs/errata/stable/ It's also been added to trunk. :) -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page

Re: UTF-8

Richard A Downing wrote: > On Fri, 20 Jan 2006 06:34:20 -0800 > Dan Nicholson <[EMAIL PROTECTED]> wrote: >>BUT, in the past when it was being decided if the book would become >>UTF-8 compatible, I remember there being a lot of support for it being >>on by default. I personally want it this way, an

Re: Perl security vulnerability

On 1/17/06, Tim van der Molen <[EMAIL PROTECTED]> wrote: > A while ago I posted on lfs-security about a Perl security vulnerability > and a patch that remedies it: > > > I thought the patch should be added to LFS SVN and

Re: UTF-8

On Fri, 20 Jan 2006 06:34:20 -0800 Dan Nicholson <[EMAIL PROTECTED]> wrote: > On 1/20/06, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote: > > > > Unfortunately, this broke jhalfs, because it assumes that the book > > has to be followed in the linear way. Further patches will not be > > provided u

Re: UTF-8

On 1/20/06, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote: > > Unfortunately, this broke jhalfs, because it assumes that the book has > to be followed in the linear way. Further patches will not be provided > until a consistent approach to this problem is developed. Manuel, please > help. Alexan

Re: UTF-8

I wrote: I have prepared a sample patch (attached, but please don't apply now) that implements the changes described by you to the Coreutils page. Does this sample look OK to you? Unfortunately, this broke jhalfs, because it assumes that the book has to be followed in the linear way. Further

Re: UTF-8

Jim Gifford wrote: With the recent thread in Cross-LFS and LFS-dev lists, I wanted to pose an idea. Couldn't we add the utf-8 pages to an appendix and refer to them via notes in the builds, like we currently do with Cracklib in Shadow, the only difference is that we would be refering to an ap