Message: previous - next
Month: April 2012

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

From: Darrell Anderson <humanreadable@...>
Date: Tue, 10 Apr 2012 18:29:34 -0700 (PDT)
> 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.

Do you mean I can't push changes to admin/cmake in each individual module because the next time I resync they all will be overwritten? That any changes I always want to make to admin/cmake must be to the common ones and they must be pushed immediately?

How do I test here before pushing to the master server? If the replication occurs only at the main GIT server, then those replications do not occur locally to all of the modules in my local tree. Seems the only way to make this change is to patch my common admin/cmake and push immediately. But then I hold my breath that I did not break anything major.

Seems as though there is a point of uncertainty whne pushing changes to the common admin/cmake. I can't simulate the replication of the main GIT server.

Perhaps I am misunderstanding the whole thing.

I also need to concurrently push the changes to tdelibs because of kstandarddirs.cpp.