Re: [boost] [cmake] revision 50756 failed to merge some file properties

Subject: Re: [boost] [cmake] revision 50756 failed to merge some file properties
From: troy d. straszheim (troy_at_[hidden])
Date: 2009-09-08 17:59:34

Joaquin M Lopez Munoz wrote:
> troy d. straszheim <troy <at> resophonic.com> writes:
> 
>> JOAQUIN M. LOPEZ MUÑOZ wrote:
>>> Unless fixed, this is going to pop up again when the release
>>> manager prepares for 1.41.
>>>
>> This should be fixed in r56113, apologies about this and thanks
>> for the notice.
> 
> Thank you for taking care.
> 
>> I suppose there is some question whether it makes sense to keep this 
>> stuff in release/trunk or not, as it is apparently only used by end 
>> users and packagers;  I take no pleasure in making the release process 
>> more difficult than it is; 
> 
> IMHO if some specific material (CMake stuff in this case)
> is going to be delivered, then it *has* to be deployed
> and maintained in trunk just as anything else; this particular
> quirk was just that, a quirk, I wouldn't extract far-fetched
> consequences from it.

 From my perspective, it isn't a quirk;  When 1.41 time rolls around,
it will make sense to tune up the cmakefiles for release, and it will 
still not make sense to tune up the cmakefiles on the trunk, where noone 
uses them.  I'm not about to ask library authors to maintain two build 
systems, nor to ask them to switch to cmake;  however I think the 
cmakeable distributions are useful to a certain group, and it is easy 
and efficient to prepare these asynchronously.

-t