Currently we have .metainfo.xml.in under bootstrap/ but final .metainfo.xml in the same directory as the binary.
There's no real reason why it's that way - likely just looked logical at the time .desktop files were added, and then .metainfo.xml files were added with the same pattern.
As seen with problems with current version of #45616, this way of having the target and source in different parts of the tree can be very hard to get working correctly with autotools. We should just generate .metainfo.xml to bootstrap/ , and to do that change as the very first step of the metainfo generation reworking (i.e. even before #45616 which is then to be reimplemented/rebased on top of that)
Like I said .desktop files follow the same pattern, and very likely we have to eventually do similar change for them, but as that's not a blocker to anything important just now, I'd leave it to later time.
Currently we have .metainfo.xml.in under bootstrap/ but final .metainfo.xml in the same directory as the binary.
There's no real reason why it's that way - likely just looked logical at the time .desktop files were added, and then .metainfo.xml files were added with the same pattern.
As seen with problems with current version of #45616, this way of having the target and source in different parts of the tree can be very hard to get working correctly with autotools. We should just generate .metainfo.xml to bootstrap/ , and to do that change as the very first step of the metainfo generation reworking (i.e. even before #45616 which is then to be reimplemented/rebased on top of that)
Like I said .desktop files follow the same pattern, and very likely we have to eventually do similar change for them, but as that's not a blocker to anything important just now, I'd leave it to later time.