What's the policy on new packages in the BLFS book? For instance I discovered an editor, called Bluefish, and introduced a number of LFSers to it, with good reports. BLFS doesn't have a tabbed desktop-independent X-windows editor designed for markup and syntax highlighting (I know emucks can do everything, thanks)
I considered a hint, and I could still do that, but also considered a patch to the svn book - which I'll probably do anyway just as an exercise. I positively dislike hints now, as I personally find the text-only format very hard to read. However, is there any mileage in new packages? I'm aware that a submitter will also need to be a maintainer - and to do that as patch submissions - which is OK. Another thought occurs - how about an optional xml format for hints, so they could be rendered as html, pdf or text? - more thinking required on that I think... R. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
