The way you described the option above, about the software scanning locally for the various things does actually make perfect sense. In other words, if the end user chooses to persist relative to the project, use it; otherwise search higher in the list in order to satisfy. Much like how we do all the things in Unix anyway...
While we're here, I've always secretly wished the .qtr file's <directory> element was scoped relative rather than as an absolute path. Reason being is that porting to a newly/freshly installed system would force me to recreate the exact path in order to recover. Not saying that's not possible but relative seems to be the move as it just avoids the issue entirely.
The way you described the option above, about the software scanning locally for the various things does actually make perfect sense. In other words, if the end user chooses to persist relative to the project, use it; otherwise search higher in the list in order to satisfy. Much like how we do all the things in Unix anyway...
While we're here, I've always secretly wished the .qtr file's
<directory>element was scoped relative rather than as an absolute path. Reason being is that porting to a newly/freshly installed system would force me to recreate the exact path in order to recover. Not saying that's not possible but relative seems to be the move as it just avoids the issue entirely.