X11 Building for Slackware ARM
------------------------------

Note that with the modular X.org, some component versions do not
change version, but need to be recompiled against the rest of
X11.

To facilitate this, Slackware as a 'build' directory containing text files
of the filenames of packages.  

Slackware ARM uses a dir named 'build-nums' for the same thing. We don't
just use Slackware's build numbers since we may need to keep our own.
(I prefered the 'build-nums' name since it was more obvious what the dir was for).
Each text file contains the previous build number and version.

The X11.SlackBuild script handles the "BUILD" numbers automatically - incrementing
them if necessary.  This can be switched off by exporting an environment
variable -- check the "indibuild" for information.

However, for major X.org upgrades, we will want to copy all of Slackware's
build numbers.  Mostly anyway -- obviously there are some times where ARMedslack
may have a higher build number than Slackware already, so there's going to be
some manual checks in here.

http://216.239.59.104/search?q=cache:CCfeSMZ0udsJ:www.robert-bruce.co.uk/package.keywords+x11+util-macros+app&hl=en&ct=clnk&cd=3&gl=uk

Additional drivers
------------------

When building a new release, Slackware doesn't include:
 - fbdev -- apparently it doesn't build

We need this for Slackware ARM.

Process:
 - Ensure the environment var in arm/build is set to not update
   BUILD numbers in package file names.  We'll be doing a few
   passes of the build, so we don't want to increment them.
   This ASSUMES that most of the packages have been updated since
   the previous release.  You'll need to do some manual checks here.
 - Run arm/build
 - Find the section in the "indibuild" script which builds the "fbdev"
   driver.  Uncomment it and then run the script.
 - Rebuild the whole lot with arm/build
 

-- 
Stuart Winter
24 Feb 2010