On 09/27/2014 08:21 AM, Alan Feuerbacher wrote:
On 9/27/2014 1:14 AM, Bruce Dubbs wrote:
Alan Feuerbacher wrote:
On 9/26/2014 8:57 PM, Bruce Dubbs wrote:
Also why do you want to add the dev environment? I suspect it is a lot
of extra space and time. Are you going to modify the ff source?
I have no clue why or why not I ought to add it. That's why I'm asking.
My motive in asking is to leave no stone unturned in trying to
understand what the BLFS book is telling you to do.
If you don't know, then you don't need it.
I disagree. The most that can be said is that I simply don't know.
My experience in nearly forty years of technical learning (I design
microchips for a living) is that when you come upon anything new, it
often pays big dividends to learn what it's about. Then you can decide
whether it's worth your time or not.
You and I have similar approaches and I'm positive that some people who
monitor this list have seriously "rolled their eyes" when I've asked
questions. But they always help. I believe in, "I don't know what I
don't know," and the answer to "Why do you want to know this?" is "I
want to know it."
I've lost track of the main thrust of this thread, but I've seen where
it has gone. I believe that the "devel environment" is the nuts, bolts,
and pieces to build TB and FF from the nightly Mozilla builds. As Ken
said, this might be a good idea for some, especially if you're helping
to test and develop these things, but the released stable versions of
both packages rarely matches. You could do this, but IMO it would be a
pain "south of the border" and in the "opposite hemisphere" to maintain
the devel environment to match the version number of the released packages.
Dan
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
