File: faq.txt
patch-22 patch-23
Line 138Line 138
The machine {gar.lnx-bbc.org} was our old development box and build
system.

The machine {gar.lnx-bbc.org} was our old development box and build
system.

GAR is also the name of our software <http://cvs.lnx-bbc.org/cvs/gar/
build toolset>. Common backronyms we've seen include "GAR Are
Recursive" and "Gmake Autobuild Runtime". It is a system similar in
function (and nearly identical in purpose) to the BSD
<http://www.freebsd.org/ports/ ports system>. It is a set of
Makefiles that we use to compile all of the software in the BBC and
turn them into an ISO9660 CD-ROM image file.
GAR is also the name of our software build toolset. Common backronyms
we've seen include "GAR Are Recursive" and "Gmake Autobuild Runtime".
It is a system similar in function (and nearly identical in purpose) to
the BSD <http://www.freebsd.org/ports/ ports system>. It is a set of
Makefiles that we use to compile all of the software in the BBC and turn
them into an ISO9660 CD-ROM image file.
The term "GAR" <http://everything2.com/index.pl?node=gar has many
definitions>, but it is most commonly used by us as an expression of
The term "GAR" <http://everything2.com/index.pl?node=gar has many
definitions>, but it is most commonly used by us as an expression of
frustration or in the context of <http://cvs.lnx-bbc.org/cvs/gar/ the
GAR system>.
frustration or in the context of the GAR system.
== Why was GAR written? ==

== Why was GAR written? ==

Line 169Line 167
before a trade show or other release deadline.

The process of taking a tree of files and directories and making a
before a trade show or other release deadline.

The process of taking a tree of files and directories and making a
compressed loopback bootable iso from it was pretty well automated,
but there was no good way of getting the tree into the proper state.
GAR downloads, checksums, patches, configures, builds, and installs
packages using only a tree of makefiles and patches. This allows it
to be <http://cvs.lnx-bbc.org/cvs/gar/ stored in CVS>, and the size of
the <http://cvs.lnx-bbc.org/cvs/gar/gar.tar.gz?tarball=1 checked-out
copy> is only a few megabytes overall.
compressed loopback bootable iso from it was pretty well automated, but
there was no good way of getting the tree into the proper state. GAR
downloads, checksums, patches, configures, builds, and installs packages
using only a tree of makefiles and patches. This allows it to be stored
in arch, and the size of the checked-out copy is only a few megabytes
overall.
== So why GAR? Why not <name-of-favorite-build-system>? ==

== So why GAR? Why not <name-of-favorite-build-system>? ==