Randy has placed Wednesday, Feb. 14th as the release date for
BLFS-6.2.0. I'd like to ask people to take a little time to review the
book and look for any changes that can improve the book before
release.
I've created a new ticket #2242[1] to collect any small issues.
Patches are welcomed.
On 2/13/07, fenna [EMAIL PROTECTED] wrote:
about midnight commander 4.6.1 (blfs chapter 11)
If blfs-6.2.0 is to follow-up on lfs-6.2, why is there a patch for a bash-3.2?
(lfs-6.2 is build with bash-3.1)
Excellent question. It shouldn't be in there if it really is just for
bash-3.2.
On 13/02/07, fenna [EMAIL PROTECTED] wrote:
If blfs-6.2.0 is to follow-up on lfs-6.2, why is there a patch for a
bash-3.2?
(lfs-6.2 is build with bash-3.1)
LFS svn uses bash-3.2, and BLFS svn reflects that with proper support
for it, by the time BLFS svn goes stable, hopefully LFS svn will soon
Book Version
This is BLFS-BOOK version svn-20070211 dated February 11th, 2007.
This is the development branch of the BLFS book, currently targeting
the LFS development book
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See
As i said before .. perfect for the SVN blfs ...
but I was NOT talking about blfs-SVN.
This page is from the blfs-6.2.0rc2 book:
http://www.linuxfromscratch.org/blfs/view/6.2.0-rc2/general/mc.html
however this is all very theoretical .. Alexander already replied to the
Wiki report I put in
[from blfs-book]
Bruce Dubbs wrote these words on 02/13/07 11:37 CST:
Just an idea.
Perhaps we should create another entities file, externals.ent that
defines all the external references and then use the entities in the book.
This would give us a nice single location for all externals
Randy McMurchy wrote:
But it made me remember about this thread from -support and sure
enough, if I pass --with-tcl=/usr/lib, then Expect configures
properly the first time through. Can anyone confirm this behavior?
I just tested it. I have to pass --with-tcl=/usr/lib for the build to
On 2/13/07, Guy Dalziel [EMAIL PROTECTED] wrote:
Book Version
This is BLFS-BOOK version svn-20070211 dated February 11th, 2007.
This is the development branch of the BLFS book, currently targeting
the LFS development book
That's the development version. We're talking about the 6.2 branch,
On 2/11/07, Randy McMurchy [EMAIL PROTECTED] wrote:
Dan Nicholson wrote these words on 02/11/07 12:47 CST:
The only problem with that one is that OPT_FLAGS becomes one really
long line. I don't know if we can format it over a single line in the
book. Adding a breakline \ before the -D
Dan Nicholson wrote these words on 02/13/07 23:01 CST:
Randy, are you planning on putting this in 6.2.0? I'm pretty confident
about the command changes, but I don't know what you had planned for
the textual changes. This page is pretty messy.
Yes, it is a bit messy. But a day or so ago I
On 2/13/07, Randy McMurchy [EMAIL PROTECTED] wrote:
Yes, it is a bit messy. But a day or so ago I decided to leave the
existing commands as is. DJ put them in there and they work. I only
tested on a current LFS-SVN, so I can't say for sure they work
(though I know they would).
I'm going to
Dan Nicholson wrote these words on 02/14/07 00:24 CST:
Sounds good. The text was the main thing I was concerned about. We can
tweak the commands later, but I'd rather not go to release with all
the note boxes there.
I'm working on it. First, some bad news about this consolidated ticket
idea
Hi all,
Sorry to be a stick-in-the-mud, and perhaps it's just me, but I don't
like this lump everything in one ticket idea (using the BLFS-6.2.0
Text Changes ticket as an example). I find it difficult (if not
impossible) to figure out:
1. What has been taken care of?
2. What is still under
On 2/13/07, Randy McMurchy [EMAIL PROTECTED] wrote:
I'd prefer if we go back to the tried-and-true method of opening a
ticket when there's an issue, and closing it when it is fixed. Perhaps
I'm just old-fashioned.
Yeah, I guess it didn't go the way I'd envisioned. I'm working my way
through
14 matches
Mail list logo
