trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

Re: [trinity-devel] Why 'kde' still in common/cmake/modules/TDESetupPaths.cmake

From: "Timothy Pearson" <kb9vqf@...>
Date: Tue, 10 Apr 2012 20:05:07 -0500
>> You do know that to update anything in cmake/ or admin/ you
>> just need to push once to main/commmon/cmake or main/common/admin and
>> the
>> system will automatically bring those changes into all other TDE
>> modules, correct?
>
> No I don't know that. Please provide the specifics!
>
> Even after the admin and cmake directories replicate (how do they do that
> --- in your nightlies or during any local build?), that will not catch
> everything. So I probably still need to make another pass to create module
> specific packages, which, if I understand you correctly, means only a
> handful of patches rather than 117.
>
> Darrell

The cmake/ and admin/ directories (and a few others such as libltdl) are
replicated into each top level module via GIT submodules.  This process
occurs continually on the TDE GIT server, and usually catches changes
within 24 hours, independent of the nightly build system.

In fact, you ***cannot*** change anything under admin/ or cmake/ in any of
the TDE modules other than common/, as your change will be detected and
reversed by the same system that keeps the submodules up to date.

Tim