Re: [boost] boost organization and installation

From: William E. Kempf (williamkempf_at_[hidden])
Date: 2002-05-03 10:38:20

----- Original Message -----
From: "Noel Yap" <yap_noel_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Friday, May 03, 2002 9:44 AM
Subject: Re: [boost] boost organization and installation

> --- David Abrahams <david.abrahams_at_[hidden]> wrote:
> >
> > ----- Original Message -----
> > From: "William E. Kempf" <williamkempf_at_[hidden]>
> >
> > > This is very possible and would have to be a part
> > of the installation
> > > process *if* the installation process followed an
> > AAM approach instead
> > of an
> > > install package approach.  If it's an installation
> > package it's the
> > > responsibility of the packager to insure he
> > doesn't package something
> > that
> > > won't work.  In both cases, though, most (all?) of
> > the boost libraries
> > have
> > > a test suite that can be used in an automated
> > fashion to ensure this.
> >
> > BTW, integration with testing is a primary goal of
> > boost build, and we
> > have achieved that... so making tests part of the
> > build/install process
> > is definitely feasible.
>
> If tests are organised on a per component basis, we
> might be able to get some info from them about what
> belongs in what package thereby allowing an automated
> componentization of Boost.  From a quick and dirty
> find through the distribution, it looks like most, but
> not all, components already have componentized tests.

Yes, but these tests won't necessarily give you any idea what the
dependencies are.

All the information we need is documented somewhere in the Boost
distribution, it's just a matter of collecting it all from the various
sources.

Bill Kempf