X.Org scripted installation / Proprietary ATI driver

Dan Nicholson dbn.lists at gmail.com
Wed Jun 18 20:07:20 PDT 2008

On Wed, Jun 18, 2008 at 5:35 PM, DJ Lucas <dj at linuxfromscratch.org> wrote:
> DJ Lucas wrote:
>> DJ Lucas wrote:
>>> Perhaps this text is easier to understand and explains the purpose a
>>> little better:
>>> ====
>>> Additionally, because of the large number of repetitive commands, you
>>> are encouraged to partially automate the build.  The commands below (or
>>> similar) can be entered at the command line to compile each group of
>>> packages (proto, libs, apps, drivers).  The wiki links on each group's
>>> page contain specific commands to compile the entire group of packages,
>>> based on the content of the wget files.
>> No responses... I'm putting this into 6.3 and trunk.  I'm also in the
>> process of a very cut down X installation and will add libXdmcp to
>> required deps for Libs (libX11).  Additionally, after review, I'm going
>> to add the extra path depth to the patch commands on the Libs page.
>> Any objections to any of the above?

No, that all sounds good to me.

> I'm also going to go ahead and kick xorg-data out of trunk, should this
> be made in 6.3?

The usefulness of xcursor-themes is definitely pretty minimal, but I
hadn't seen it be totally deprecated upstream. Did I miss something?


More information about the blfs-dev mailing list