Add "old" and "test" subdirectories to MASTER_SITES

 

Support building of BUILDDEPS to alternate images, i.e. the native* images.
There are some caveats to actually doing this.  For example, this should build
a singularity toolchain and install it in your home directory:

GAR_BUILDDEP_IMAGE=native_home make -C lang/c DESTIMG=singularity build

However, this presupposes that you're going to keep images/singularity/image
(singularity's DESTDIR) where the singularity's glibc and kernel headers will
have been installed.  You're only a make super-clean away from losing that and
making the toolchain basically useless.  So really you could only build dep
branches this way and have them permanently available if the deps for the
branch stay within the bounds of BUILDDEPS.  Run a showdeps before you build to
verify.

It doesn't make any sense to override GAR_BUILDDEP_IMAGE with the name of a
cross-compiled DESTIMG, so don't do it unless you're really into that sort of
thing.

 

Hurg.... an URL with an IP for a hostname.  Oh well, that's where the link from
the official arping website points.

 

Upstream has decided not to retain old versions of xfsprogs at the main
distribution point.  I'm not sure what the legal ramifications are regarding
the GPL's three-year availability requirement.  I suppose since SGI doesn't
actually distribute binaries (or do they?), it's actually incumbent upon those
who do (distros) to keep copies of this tarball around.

 

Add ftp://sources.redhat.com/pub/lvm2/old/ to MASTER_SITES.

 

GARBUILD is set using an autoconf config.guess script, but it should only do it
once because it's kind of slow.  Cache it in the environment.

 

The value of STAGINGDIR has to be an absolute path.

 

So the star-merge source tree needs to synced before the star-merge..... live
and lurn.

Patches applied:

 * inkblot@movealong.org--projects-2004/lnx-bbc--gar-extraction--1--patch-12
   Whoops, got to update this one first

 

meta/singularity uses depmod in the build-custom target.  Most systems have
depmod, but it might be the wrong one (modutils vs. module-init-tools) or it
might not be one of those systems (static kernel/build chroot/etc).  Add
kernel/module-init-tools to BUILDDEPS and then run it by absolute path (this
isn't strictly necessary, is it?).

 

garchive depending on checksum causes major throttling issues on i/o limitted
hosted servers (linode.com).  It should depend on checksum by default, but with
the option of overriding

 

Patches applied:

 * jjenning@fastmail.fm--lnx-bbc/lnx-bbc--latency--0.1--patch-1
   build fixes

 * jjenning@fastmail.fm--lnx-bbc/lnx-bbc--latency--0.1--patch-5
   use ip in scripts instead of ifconfig and route

 * jjenning@fastmail.fm--lnx-bbc/lnx-bbc--latency--0.1--patch-6
   document the ip command

 * jjenning@fastmail.fm--lnx-bbc/lnx-bbc--latency--0.1--patch-7
   whoops, forgot the checksums

 * jjenning@fastmail.fm--lnx-bbc/lnx-bbc--latency--0.1--patch-9
   trivial-net-setup backquote fixes

 * jjenning@fastmail.fm--lnx-bbc/lnx-bbc--latency--0.1--patch-10
   whoops, forgot checksums again

 

Lots of "unsupported compiler options" in the ccache stats... perhaps a new
version will help.

 

Make the DESTIMG definitions more specific, so that they expand to the proper
value regardless of the value of DESTIMG.

Also, slightly less science in devel/gcc/Makefile.  $(shell which $(build_CC))
is /usr/lib/ccache/gcc on my system, and similar on any other ccache-using
system.  This is sort of defeatist since this is exactly the case that the line
of code in question is trying to account for.

 

Be a bit more precise about what files to touch in post-install.

 

26 precious patches.

 

This is a little piece of insanity that's been nagging at me for a long time.
Every time make is invoked with the meta/lnx-bbc Makefile, the version is
different.  This stabilizes it somewhat so that if you actually perform a build
(i.e. any GAR step that causes pre-everything to run) the version is locked to
that timestamp until the package is cleaned.  I intend to make good use of this
stability in the autobuild script.

Also, put the full path of the image in IMAGE_PATH.  This is also for the
benefit of the autobuild script.

 

This guy over at OSDL is apparently now generally recognized as the official
upstream for iproute2, and there are NUVs to be had.  It still uses a goofy
hand-crafted configure script which makes horrible, horrible assumptions about
build and host platforms (i.e. assumes they are one in the same).  Also, arpd
uses a bdb for something or other.

 

I'm not really even sure what the main upstream distribution point for this
package is, but the one we've been using is apparently haven't extended
technical difficulties.  Add a mirror to compensate.

 

Linux 2.6 has a new set of module utilities to service it's dynamic end.  They
are in kernel/module-init-tools and the package is functional, so this swaps
out the old defunct kernel/modutils in favor of the new.