Discussion about a new BLFS release

DJ Lucas dj at linuxfromscratch.org
Mon Nov 22 09:45:04 PST 2010

"Robert Xu" <robxu9 at gmail.com> wrote:

>On Mon, Nov 22, 2010 at 02:13, DJ Lucas <dj at linuxfromscratch.org>
>> On 11/21/2010 06:53 PM, Randy McMurchy wrote:
>>> DJ Lucas wrote these words on 11/21/10 17:52 CST:
>>>> I'm using 20101117 version. Might be pushing it a bit, but I'm sure
>>>> wind up rebuilding anyway at some point. Next question is whether I
>>>> should revisit the update to Xorg-7.6. I think I'm going to go
>ahead and
>>>> push forward with it. A lot of people have been building against
>>>> already with only one issue to speak of.
>>> I can say that what we have in the book right now (pixman must be
>>> to support the version of Cairo I am going to update to) works
>great. If
>>> you want to update, great. I'm ready to seriously think about a
>>> (without KDE), so do what you feel is best.
>> Actually, I was really wanting to get Trinity into the release, but I
>> haven't used KDE in a *long* time. Might take me a bit to catch my
>> bearings, but I imagine I could have my first build done by Tuesday
>> Wednesday evening. I don't expect the Xorg update to be too invasive.
>> I'm also not expecting that Trinity will be all that different from
>> KDE-3.5 as far as explanatory and descriptive text is concerned. At
>> worst case, I can start on it. If it is not done by time for package
>> freeze, then we can simply remove the entire section temporarily (as
>> KDE, in its current state, does not build I'm told).
>Nope. It does not.
>FYI I have dependencies for a minimal Trinity in this order:
>- tqtinterface
>- arts
>- kdelibs
>- kdebase
>- kdebindings
>and then whatever you want after that.
>As I mentioned before, you need autoconf 2.63 or lower to generate the
>configure files... A real pain.
>cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
>cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
>make -f admin/Makefile.common
>Someone is working on a cmake version, but it's not done yet.
>I'm thinking, could we make like a temporary autoconf 2.63 installation
>in /opt?

Overkill IMO, but doable.  I'd rather just regenerate the files and distribute, though it would be cool to show how to use a local copy.  Also, what is wrong that newer autoconf can't do the job?

--DJ Lucas

Sent from my Android phone with K-9 Mail. Please excuse my brevity.

This message has been scanned for viruses and
dangerous content, and is believed to be clean.

More information about the blfs-dev mailing list