[Boost-build] Consistent toolset versioning requirements :(

From: David Abrahams (dave_at_[hidden])
Date: 2006-10-10 09:59:07

  error: gcc initialization: parameter 'version' inconsistent
  error: no value was specified in earlier initialization
  error: an explicit value is specified now

We've discussed this problem before.  Any site administrator who
invokes "using gcc ;" in site-config.jam prevents users from
initializing gcc with a version.  Any site administrator who adds a
new "using" invocation to site-config.jam (even a versioned one)
potentially breaks the user-config.jam of any users.

The only safe thing for everyone concerned is to never invoke "using"
without a version identifier:

    using gcc : default ;

but after all, isn't that just redundant?  The system could simply do
that for me.  And finally, it won't work for the Python toolset, for
example, which expects that 2nd argument to be a real, meaningful
toolset version.

Why do we still have this requirement that "using" be invoked
consistently?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com