I successfully compiles OpenOffice 2.2.1 from BLFS Development Book on
BLFS 6.2.0
System. I used default values for configuration without --enable-cairo
with --enable-kde
--with-firefox --with-system-mozzila and with KDEDIR=/opt/kde-3.5.6
Sami Tarazi
--
http://linuxfromscratch.org/mailman/lis
I could have expanded on those two areas a bit more.
What I specifically meant by free-form, was that software packages could be
added to the wiki easily and consistently. And have it organized by
software then by version of the software so that even if a specific build
was needed than it could be
Hi.
Daniel Myers wrote:
> First, could have a little more free-form wiki, free-form more being in what
> is added or included in the wiki. So if someone were to build openvpn say
> for example's sake, they could add an entry to the wiki on openvpn.
> Organize the entries by software, and version
Hello,
I had actually been thinking about a couple of things of related note here.
First, could have a little more free-form wiki, free-form more being in what
is added or included in the wiki. So if someone were to build openvpn say
for example's sake, they could add an entry to the wiki on open
Hi Bruce,
Thanks for the reply. Some of your points I foresaw, but that doesn't
invalidate them.
Bruce Dubbs wrote:
> 1. Each page of the BLFS has a link to a wiki page. Users are free
> to add to them, so you can help the community there if you would like.
Sure. But now you have 2 pages, a
