#136: Don't rebuild external libraries so often --------------------------+------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: review Priority: minor | Milestone: Component: Cactus | Version: Resolution: | Keywords: --------------------------+-------------------------------------------------
Comment (by anonymous):
I think we might be converging on a solution, but we also have two problems at hand here. Let's try to disentangle them.
1. We might want to use a library location outside of Cactus, but still we would like Cactus to build that library.
A user would have to specify that location. It might be useful to do that for each library separately, but it might also be of interest to have one switch to build all libraries in some specified place.
2. Regardless of the location being inside or outside of Cactus it should be possible to avoid too many rebuilds (the original intent of the ticket) in an automatic fashion.
Here we could, as described above, let the user specify that location, or choose some default within the Cactus tree for that, possibly containing the configuration name, but for sure containing the configuration options in a file. Then Cactus can compare configuration data of different configurations within subdirectories there, and figure out by itself if a library needs to be rebuilt, or if an existing version can be used.
Solving problem 1 needs user interaction to avoid rebuilds, solving problem 2 would make it work automatically, but is also more work to implement.
I suggest we go ahead with the current patch, and keep this as overwrite even if we implement something for problem 2.