Pack only considers a local package to be "outdated", when a change happened to one of the files in the package's source directory. However, if one only changes a package's .ipkg file, for instance, to add a missing module, the packge is not considered to be outdated and hence, it is not reinstalled when we build other libraries having the original package as a depenency.
This PR fixes exactly this: A package is now also considered to be outdated when its .ipkg file has a newer timestamp than the .timestamp file installed together with the package's compiled artifacts.
Pack only considers a local package to be "outdated", when a change happened to one of the files in the package's source directory. However, if one only changes a package's
.ipkgfile, for instance, to add a missing module, the packge is not considered to be outdated and hence, it is not reinstalled when we build other libraries having the original package as a depenency.This PR fixes exactly this: A package is now also considered to be outdated when its
.ipkgfile has a newer timestamp than the.timestampfile installed together with the package's compiled artifacts.