#1897: MPI thorn builds when it shouldn't ------------------------------------+--------------------------------------- Reporter: hinder | Owner: Type: defect | Status: review Priority: blocker | Milestone: ET_2016_05 Component: EinsteinToolkit thorn | Version: development version Resolution: | Keywords: MPI ------------------------------------+--------------------------------------- Changes (by knarf):
* priority: critical => blocker * status: confirmed => review
Comment:
After conversation with Erik, we came to the conclusion that it seems we need two files to indicate the two different things we need. We need one file to indicate that the thorn is done, and whose date only updates if something in that thorn was updated (done), and we need another file that indicates that the library in external thorns is available, either built or available otherwise. The date of that file has to update whenever that library changed (when built). That second file can be considered 'internal' to that thorn. We considered two possible names for that file: build_unnecessary_or_complete or available. If no objections are raised and no other names are proposed, it will be 'available'. This will need to be changed in all external libraries, and is a release-blocker because currently libraries are built even if they are supposed to not be.