Alexander E. Patrakov wrote these words on 03/04/08 02:18 CST:

> IMHO, BLFS-6.3 has already missed the train and thus should not be
> released at all (of course, with an official announcement that there
> will be no release). Look: the LFS book says at
> http://www.linuxfromscratch.org/lfs/view/stable/chapter01/changelog.html:
> 
> This is version 6.3 of the Linux From Scratch book, dated August 28,
> 2007. If this book is more than six months old, a newer and better
> version is probably already available.

I believe we can get a 6.3 release out to match the 6.3 LFS book.
Sure, it may be outdated, but it's stable enough for release.


> And yes - there is a book in SVN. As for tickets, I think that some
> cleanup is needed.
> 
> As a first step, I propose to remove autofs, because it has four
> tickets about its bad state, which confirm that the editors don't use
> this package and can't maintain it:
> 
> #2458 (about a woefully incorrect example and a missing
> overview/comparison with HAL-based methods)
> #2250 (about the latest upstream patches not being in the book)
> #2310 (about a year-old typo in the initscript)
> #2416 (version update)

I'm indifferent on this one. I've never used it, and can't see
ever using it. If nobody else comments, I'll remove it (comment
it out).


> Then, remove Dillo (#2226 - dead upstream)

How about a compromise on this one? We add a note saying that
Dillo does not handle UTF properly, but leave it in the book
for the 6.3 release.


> and Links (wish by Randy if
> an agreement with Ag cannot be reached, see #2276 and the recent
> discussion on blfs-dev).

There's an open ticket on this one, so it will be addressed one
way or another.

-- 
Randy

rmlscsi: [bogomips 1003.22] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686]
09:36:02 up 18 days, 1:21, 1 user, load average: 0.35, 0.22, 0.19
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to