[bind10-dev] Big fat tarball for releases?

Shane Kerr shane at isc.org
Mon Jul 18 15:48:21 UTC 2011


All,

As I was downloading building packages for the various BIND 10
dependencies last week, I thought, "maybe we can just put all of these
in a tarball".

We've been careful about licenses, so we should have no problem actually
distributing any of the libraries we depend on.

What I'm thinking is that we can also make something like:

bind10-devel-2010-08-16-bigfat.tar.gz

Which would have a directory structure something like:

INSTALL
README
bind10/
configure
dependencies/

The "bind10" directory would be BIND 10, and "dependencies" would have
source code for each of the libraries we depend on.

"configure" could be very stupid, and just build everything, or it could
be smart and do tests to see which libraries are already installed on
the system before building each one. (I'd probably download this version
myself for every system I use, to avoid having to go through SourceForge
to get to log4cplus, if it was smart about builds.)

The downsides are that:

      * People might send bug reports for dependencies to us, and we
        can't help them. (We should try to make it clear that people
        should use supported software, like something from their
        distribution packages.)
      * We have to try to keep this stuff more-or-less up to date. None
        of these packages moves especially quickly, but we don't want to
        fall too far behind, so probably we'd want to check every
        release or so, which means more work for each release.
      * We need to add the big fat tarball to our build farms. Probably
        not triggered on every code change, but at least before each
        release or when we update or add a library.

The upsides are that people can just download a single tarball
and ./configure && make && make install. :)

Thoughts?

--
Shane




More information about the bind10-dev mailing list