Jeremy Huntwork wrote:
> Oh yeah? I'll give you something to sigh about...
>
> /me dips Archaic's hands in maple syrup and tacks pages of 'War and
> Peace' to them.
Hrm. Doesn't seem to have worked... :/
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfroms
* Alexander E. Patrakov <[EMAIL PROTECTED]> [2006-01-05 16:48]:
> Jeremy Huntwork wrote:
>
> >It would definitely help the workload if some packages in BLFS were
> >removed. For starters, perhaps BLFS could employ a policy that any that
> >are just a simple CMMI install (or ones which are easy to
Archaic wrote:
> That's all that is needed. We don't *need* to implement some fancy
> technology. You don't even have to submit it as a hint, as you have an
Many of us don't have *need* for X on our desktops either, but we add it
and a window manager, and scores of other packages, because it's ni
Jeremy Huntwork wrote:
I think I still prefer the wiki. And re-establishing a properly
moderated and full-featured wiki could benefit the entire LFS community
once again, not just BLFS. The only reason our old wiki was dropped was
because of lack of use and poor moderation. If we have more regu
Jeremy Huntwork wrote:
Trac could provide a wiki and replace bugzilla with one swoop (and there
are other benefits).
BTW, I know Matt at one time wanted to know if Trac could import
databases from Bugzilla.
http://projects.edgewall.com/trac/wiki/TracImport
--
JH
--
http://linuxfromscratch.o
Bruce Dubbs wrote:
>>From that form, an editor would review submitted comments and approve
(with possible edits), reject with comments, or discard the input.
Approved comments would be inserted into the appropriate html page as a
part of the daily book generation, but not the pdf form of the boo
Jeremy Huntwork wrote:
> Bruce's original email seemed to imply that additional work is a
> consideration.
It is a consideration, but the most important issue is qualification to
make the appropriate changes. The editors do not have the
qualifications to make appropriate changes in every area.
I had another thought about how to go about how to support clfs, i18n,
etc. Perhaps we could initiate a "User Contributed Notes" section that
could be submitted by a general user similar to the php documentation.
For example see:
http://www.php.net/manual/en/language.variables.php
As I envision
On 1/4/06, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
> 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
Bruce Dubbs wrote:
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 in
10 matches
Mail list logo
