Dan McGhee wrote:
> I hope I'm not sticking my nose in where it doesn't belong.
Please comment here. You are welcome.
> And a question: Should I take the reports of success and failure to the
> support list, or are they OK here?
We are developing xorg7. It is not in the book. This is precisely the
correct forum.
> The main thing I have taken from my builds of {,B}LFS is the learning.
A classic blfs 'user'. :)
> So I'm going to address only 7.0.
>
> That install looks rather mundane also except that one must worry about
> build order and decide whether or not to "copy and paste" './configure
> && make && make install' a couple of hundred times or whether to script.
Not much learning in doing CMMI over and over.
> Additionally, there's the choice of what to include in an individual
> Xorg build. I came away from Windoze and linux distros because I had to
> install a lot of stuff I never used or that didn't apply to my
> hardware. That same thing is true of Xorg 'til now.
>
> My recommendation is to include, basic (define basic) instructions for
> all three of these methodologies in "the book." I'm sure that there
> will be a lot of "I want to just click and have it install" or "How do I
> make this script run" questions. My solution is to sic Randy on 'em.
> :-). I've already seen a complaint that DJ's method has "too many
> instructions." That's like a musical piece having too many notes.
In KDE there are about 20 packages. Each one has multiple applications
that can be built. We do mention that you can set a DO_NOT_COMPILE
variable, but the default is to build everything in a package. This
general approach is probably applicable to xorg7 too, although the
details will be different.
In some ways, I see the xorg7 build to be like the bash scripts
section--long and somewhat repetitive, but also showing dependencies so
users can customize as desired.
In the end, I think that most users will build everything because they
don't know if they need something or not and don't want to go back if
they forgot something. A set of scripts for each major section seems to
be the right way to go.
> I'm getting too philosophical now and this is already too long. Thanks
> for bearing with me. It's time that I began to stop taking from {,B}LFS
> and start giving back.
I think that's great. We welcome your input.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
