Recently there has been a lot of activity in the LFS community. There
has been especially important activity in internationalization (i18n)
and cross-LFS (CLFS) that has the potential to to expand the horizon of
BLFS significantly.
We have already started putting some i18n into the book and the CLFS
team has asked us to add support for multi-lib and other related issues.
Additionally, there are new packages that should be added to satisfy
dependencies of packages already in the book.
The problem is that BLFS is already at 1082 pdf pages (488 html files).
There are 104 outstanding bugs and that list seems to be growing. In
other words, we are having trouble now keeping up.
The way I look at it, we have four possibilities:
1. Ignore the issues.
2. Add i18n / CLFS issues to each package as they come up.
3. Have a section or appendix in the book to address the issues and
link each package to the appropriate part. This is the approach
that has been taken for i18n so far.
4. Link each section of the book, as required, to an external wiki/web
page to address i18n or non-x86 issues.
#1 is not really acceptable because it is not being responsive to the
community.
#2 and #3 are essentially the same with the location within the book
different. They do nothing to address the workload issues.
I lean toward #4 right now because it would basically take the BLFS
editors out of the non-mainline issues and let the experts in each area
update as needed. We also have additional servers available that can
distribute the load away from belgarath if necessary.
I would like to open up a dialog of how to best handle the desires of
the community. Also, the above list is not necessarily exhaustive.
Other proposals would certainly be appropriate as a part of the discussion.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
