Re: [boost] [regression] OK to merge? Should tools/regression be a submodule?

Subject: Re: [boost] [regression] OK to merge? Should tools/regression be a submodule?
From: Beman Dawes (bdawes_at_[hidden])
Date: 2014-01-03 21:44:44

On Thu, Jan 2, 2014 at 7:05 PM, Edward Diener <eldiener_at_[hidden]>wrote:

> On 1/2/2014 2:43 PM, Daniel James wrote:
>
>> On 2 January 2014 18:54, Edward Diener <eldiener_at_[hidden]> wrote:
>>
>>> On 1/2/2014 11:24 AM, Beman Dawes wrote:
>>>
>>>>
>>>> On Thu, Jan 2, 2014 at 10:29 AM, Daniel James
>>>> <daniel_at_[hidden]>wrote:
>>>>
>>>>  On 2 January 2014 14:50, Beman Dawes <bdawes_at_[hidden]> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> * Should tools/regression be a submodule?
>>>>>>
>>>>>
>>>>>
>>>>> Should it be part of the boost tree? Since it downloads boost into a
>>>>> subdirectory, it looks like something that exists outside of the tree.
>>>>>
>>>>>
>>>> Good point. The same might be true of several other tools, like
>>>> tools/inspect.
>>>>
>>>
>>>
>>> I do not see why a tool which manipulates the Boost tree totally outside
>>> of
>>> git should not be part of the Boost tree. One thing ( manipulating the
>>> Boost
>>> tree in some way ) does not preclude the other ( being part of the tree
>>> ) in
>>> my mind. Clearly the Boost tree can be changed locally outside of what
>>> git
>>> does in regard to version control.
>>>
>>
>> Nothing is precluded, but separating things makes life easier. Is
>> there a reason why it needs to be part of the tree?
>>
>
> If it needs to know where the Boost tree is at, then keeping it in the
> Boost tree seems right, since it can use relative paths to find what it
> needs. OTOH if there is no dependency on anything else in the Boost tree,
> by all means make it separate.
>

It really will make maintenance simpler if the files in tools/regression
are their own project with their own public repository. That's important.

So far, all our separate tool projects are treated as sub-projects by the
boost super-project. But that's more from the habit of thinking of them as
part of the boost repo than from any strong technical need.

--Beman