Re: [boost] [trac] "Building Boost" vs. "build"

Subject: Re: [boost] [trac] "Building Boost" vs. "build"
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2010-06-07 07:47:30

----- Original Message ----- 
From: "Vladimir Prus" <vladimir_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Monday, June 07, 2010 12:05 PM
Subject: [boost] [trac] "Building Boost" vs. "build"

> 
> 
> It looks like somebody went via Trac and moved some issues from the
> "Building Boost" component to "build" component. See, for example:
> 
> https://svn.boost.org/trac/boost/ticket/4147
> 
> I certainly appreciate help with triaging issues, but in general, such
> change seems wrong -- "Building Boost" is for issues affecting exactly
> that -- building boost, while the 'build' component contain issues
> that are not necessary affecting Boost C++ Libraries at all.
> 
> Unfortunately, the changes are all anonymous, so it would be great if whoever
> made them speak up, and discuss the rationale.

Hi,

Sorry if I was wrong while changing the library? 

I recognize I was wrong changing #4147. Let me know if I must revert the change for the other.
#3625    python detection randomly broken     new    vladimir_prus    Bugs    build    104 minutes
#3904  installing boost 1.42 does not update all include files in the destination directory  new  vladimir_prus  Bugs  build  106 minutes
#4243  darwin.jam: -mmacosx-version-min not passed to compiler  new  vladimir_prus  Bugs  build  107 minutes
#3993  target-os=linux should imply threadapi=posix  new  vladimir_prus  Bugs  build  2 hours

BTW. I though that I was logged in.

Best,
Vicente