Comments on Trac ticket mails

I noticed two things in the many mails I'm receiving from the Trac ticket system: 1. The subject lines always start with the full project name in square brackets and the ticket number. Example subject: "[Linux From Scratch] #1715: bash-3.1.010". This is unfortunate, because when the subject can't

Re: Comments on Trac ticket mails

Alexander E. Patrakov wrote: [...] > > If the text is not US-ASCII and the content-transfer-encoding is > quoted-printable, all non-ASCII bytes are converted to the "=XY" > notation, where X and Y are hex digits. ASCII pats of the message are > readable with vim this way, [...] So quoted-printabl

Re: Comments on Trac ticket mails

Gerard Beekmans wrote: > It can be made more clear. And is the project name truly necessary in > the Subject header. We already know which project a ticket belongs to > based on the mailinglist it was sent to (this of course is me assuming > most everybody uses separate email folders to filter emai

LFS 6.1 and 6.1.1, chapter 3: man-pages-2.01 download location

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello! Chapter 3.2 of LFS 6.1.1 http://www.linuxfromscratch.org/lfs/view/6.1.1/chapter03/packages.html> lists http://www.kernel.org/pub/linux/docs/manpages/> as download location for man-pages-2.01. This package is not/no longer available from this l

Re: Hint on installing autotools versions in parallel

Hallo, Tushar Teredesai wrote: Finally, I have written a draft hint on installing multiple autotools version. I would appreciate your comments before I submit the hint. The hint and attachments are available at . Thanks for this hint, Tushar! autoconf

Re: LFS-alphabetical: groff before perl

Dan Nicholson wrote: Who hates the perl build system? I do, I do. Me too. %-| I can't tell you how long it took to figure this out since it appears the perl build system was written by a high school student. ??? ;-) Now, we could just add some mandir= type statements to configure.gnu, bu

Re: [locale] nano version

Alexander E. Patrakov wrote: > The question is how the book should handle this. Valid options: > > 1) Upgrade nano to 1.3.9 and briefly explain the reason on its page. > Don't add anything to the "locale related issues" page because the issue > is completely resolved. > > 2) Keep both nano-1.2.5

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

Jim Gifford wrote: [Man and groff UTF-8-ready by March, according to their respective maintainers.] > Both also expressed and interest for us > to assist in testing. Great! I'll try to help with some testing on LFS and LFS-like systems. I don't claim to know as much as e.g. Alexander about these t

Re: expect-5.43.0

Greg Schafer wrote: > This may be unrelated, but please note there has been a screwup at the > upstream tarball site. My "upstream tarball detector" script found this: "Upstream tarball detector" - cool! :-) > - [BIN] expect-5.43.0.tar.gz 08-Feb-2005 16:45 513K > + [BIN] expect-5.43.0.tar.g